we have ported a big C++ project from make approach to bjam. It works well beside of the small issue, that all compiler calls using the absolute path to the source file. For example ‚gcc.compile.c++ /home/master/project/sub1/source1.cxx‘ or ‚gcc.compile.c++ /home/master/project/sub4/source2.cxx‘. The point, we use ccache to speed up the compile times and it works well if the build is always done in the same directory, starting with for example /home/master. But if another developer try to rebuild the whole system in his own home directory, for example /home/developer1, then the ccache isn’t fetching the obejct file, because the source files doesn’t match.


Is there a way to prevent the compiler calls using the absolute path and instead using the relative path for example ‚gcc.compile.c++ project/sub1/source1.cxx‘ or ‚gcc.compile.c++ project/sub4/source2.cxx‘?

Freundliche Gruesse / Best Regards / Met vriendelijke groeten

Frank Häfemeier | Solution Architect
Am Limespark 2, 65843 Sulzbach, Deutschland
T: +49 6196/7742-511 | M: +49 171 3817790
frank.haefemeier@ogica.com | www.logica.com

Logica Deutschland GmbH & Co. KG Zettachring 4, 70567 Stuttgart; Amtsgericht Stuttgart HRA 722072

Persönlich haftender Gesellschafter: Logica Deutschland Verwaltungs GmbH Geschäftsführer: Torsten Straß (Vors.) | Philipp Behr | Steven Blythe | Dr. Markus Feidicker | Olaf Scholz | Oliver Starzonek
Handelsregister: AG Stuttgart HRB 724084


Think green - keep it on the screen. This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you.