TeeRecompile pathes for TeeTree
Posted: Fri Apr 29, 2016 8:21 am
Hi,
would it be possible to change how TeeTree-Pathes where used, when the library is compiled?
At the moment there is no way to have two seperate pathes for the Release and Debug versions of TeeTree.
It seems as if it doesn't even respect the settings in TeeRecompile and uses a hard-coded path to:
<TChart path>\TeeTree\Compiled\..
regardless of the settings of the "Debug packeages compilation" checkbox.
It would be really great if you could use the "Relative Destination:" (I'm using "..\Release" and "..\Debug") from that inputbox (relative according to TeeTree OR just put it into the same directory as the TChart-Lib).
BTW.: It would be nice if you could store that "Relative Destination" - path twice, depending on the setting of the "Debug packages compilation" checkbox. This way it wouldn't be neccessary to type that part in, each time a config needs to be rebuilt.
would it be possible to change how TeeTree-Pathes where used, when the library is compiled?
At the moment there is no way to have two seperate pathes for the Release and Debug versions of TeeTree.
It seems as if it doesn't even respect the settings in TeeRecompile and uses a hard-coded path to:
<TChart path>\TeeTree\Compiled\..
regardless of the settings of the "Debug packeages compilation" checkbox.
It would be really great if you could use the "Relative Destination:" (I'm using "..\Release" and "..\Debug") from that inputbox (relative according to TeeTree OR just put it into the same directory as the TChart-Lib).
BTW.: It would be nice if you could store that "Relative Destination" - path twice, depending on the setting of the "Debug packages compilation" checkbox. This way it wouldn't be neccessary to type that part in, each time a config needs to be rebuilt.