The problem is that I don't call perl directly... It is being called from within the openssl sources...
I can find perl perfectly with the FindPerl script, but somehow the add custom command doesn't take the PATH variable into account when running... On 05/03/2008, Bill Hoffman <[EMAIL PROTECTED]> wrote: > Steven Van Ingelgem wrote: > > Hi, > > > > > > I am under Windows (VS2003). > > > > If I run "ADD_CUSTOM_COMMAND", does the "COMMAND" run like a "cmd" > > environment? In particular looking at the PATH variable? > > > > I ask this because the output of my script indicates it cannot find > > "perl", which is perfectly accessible because I added it to the > > environment variables for both the user and everyone. > > > > Is there somehow I can fix this or is this an issue with CMake? > > > > The best thing to do would be to use find_program to find perl, then use > a full path to Perl in the custom command. PATH's can change and are > often different inside IDE's. Full paths always work. > > > -Bill > _______________________________________________ CMake mailing list [email protected] http://www.cmake.org/mailman/listinfo/cmake
