Scott Johnson wrote: > I am having some troubles with jam, mostly because I really don't know > what is going on with jam's msvcgen script. Basically, I have the > system configured to generate project files, and link everything, and it > works great. My problem is that while I am debugging, I have a few > things hardcoded such that they depend on the executable being in > $(TOP)/bin. Right now, when msvc compiles everything, it places it in > $(TOP). I was wondering if there is a way to get it to place it in > $(TOP)/bin instead. Of course, I could change it in the project, but > that would be pointless, because once the project is re-generated with > jam, it's going to go away. So, my question is where can I change this > in the jam or msvc scripts, so that it copies the output file from > $(TOP)/out/debug8..etc to $(TOP)/bin, instead of $(TOP).
The quick and dirty way would be to edit mk/msvcgen/projectx7.tlib (or projectx6.tlib if you are using an old MSVC). Find the 'linker_common' block and change the definition of 'OutputFile'. By default, it is set to 'path([my.doc.buildroot.0, my.doc.target.0])', which means that the executable path is composed of the root build directory plus the target name (the .exe file). For your hacked case, you could insert a literal 'bin', as in: path([my.doc.buildroot.0, 'bin', my.doc.target.0]) The path() macro is defined in mk/msvcgen/macros.tlib. -- ES ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Crystal-main mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/crystal-main Unsubscribe: mailto:[EMAIL PROTECTED]
