For Windows, % is not a good choice. Windows will try to interpret them as either System Variables %VarName% or batch file parameters %1.
-----Original Message----- From: boinc_dev [mailto:[email protected]] On Behalf Of Bernd Machenschalk Sent: Friday, February 26, 2016 1:00 AM To: Christian Beer <[email protected]>; BOINC Developers Mailing List <[email protected]> Subject: Re: [boinc_dev] automatic filename extension in windows wrapper Speaking about wrapper: would it hurt anyone if the "macros" (NTHREADS, GPU_DEVICE and in particular PROJECT_DIR) would be replaced in the complete command-line passed to the worker _after_ the arguments to the wrapper have been added (<append_cmdline_args/>)? This way one could pass "resolved" file names to the "worker application". One possibly needs to circumvent the shell interpretation of '$', e.g. by using '%' ('"%PROJECT_DIR") on the command-line. Bernd Christian Beer wrote on 25.02.16 21:09: > Hi, > > we have a use case where we want to use the wrapper to deploy a legacy > application. The application is bundled in a zip archive that is > extracted by the wrapper into the slot directory. This application is > called "LegacyApp" and "LegacyApp.exe" on Linux and Windows > respectively. Now comes the problem. We want t include the job.xml file > as part of the workunit not the appversion. This way we can only set one > name "LegacyApp" which causes problems because for an unknown reason > Windows 7 will not start a file without the .exe extension. > > I looked through the code and found a place > (https://github.com/BOINC/boinc/blob/master/samples/wrapper/wrapper.cpp#L633) > where we could add some more logic to detect such a case and add the > ".exe" extension. Something like: if on windows and app_path does not > exist try app_path+".exe" > > Another possibility would be to also add the .exe extension to the linux > executable but who want's to do that? And remember it later when we > wonder why we fixed a Windows Problem on Linux. > > Any thoughts on that? > > Regards > Christian _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address. _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
