Custom build binaries Path

Login to reply to this topic.
Wed, 2008-07-02 07:08
jupitar
Joined: 2005-04-13
 Forum posts: 120

Hi,

As we build the application from any directory, the build binaries always goes into the respective folders as release\winscw\udeb, UID\, & as specified in TargetPath, which are generally independent of location of your source code. My query is to coustomize the targetpath automatically, so whenever i change the codebase location on my system, the build binaries path should also get changed in the epoc folder.
e.g.
my codebase in \dir1 , so i want my binaries in \epoc32\release\winscw\udeb\dir1\
and if my codebase in \dir2 , then i want my binaries in \epoc32\release\winscw\udeb\dir2\

And i think, It could be possible if i could use a configurable variable for targettype in mmp or in custom makefile.
Please let me know how can i make Targettype configurable if possible? or is there any way using STL/openC? or any other feasible way?

PS: I consider this solution only for emulator builds, for phone release its fine to adhere with basic file system(or data caging) as it is existing, presently.

Jupitar

Thu, 2008-07-03 17:04
alh
Joined: 2004-11-29
 Forum posts: 1156
Re: Custom build binaries Path

It's a bit fuzzy what you want to achieve with this?

If you build binaries to any other folder then the udeb\ or urel\ folder, you will not be able to execute them in the emulator..

For configuring target-type, I think it works fine by just using the pre-processor (never tried though, but see no reason why it wouldn't);

#define KMyTargetType lib

TARGETTYPE KMyTargetType

If you want you can ofcourse put it in a .h file and #include it into your mmp file.

 
  • Login to reply to this topic.