Home » Community » U++ community news and announcements » Custom build steps upgrade
Custom build steps upgrade [message #34499] |
Fri, 25 November 2011 23:47 |
|
mirek
Messages: 14039 Registered: November 2005
|
Ultimate Member |
|
|
Getting ready for W++ development, I decided that we need something to move "website related" (based on extensions) files from package to .exe directory.
A good candidate was "Custom build steps", so I have upgraded it to achieve this task by adding embedded "cp" command and a couple of new variables.
The required task can now be achieved by
cp $(PATH) $(EXEDIR)/$(PACKAGE)/$(RELPATH)
List of actual Custom build steps features is available in its definition dialog in theide...
Mirek
[Updated on: Fri, 02 December 2011 09:45] Report message to a moderator
|
|
|
|
|
|
|
Re: Custom build steps upgrade [message #34626 is a reply to message #34624] |
Fri, 02 December 2011 12:00 |
Mindtraveller
Messages: 917 Registered: August 2007 Location: Russia, Moscow rgn.
|
Experienced Contributor |
|
|
mirek wrote on Fri, 02 December 2011 13:13 | What about EXEPATH, EXEDIR, EXEFILE instead?
OUT* is tied to "current file", which is problem for "phony" filename...
|
If I understand you correctly, EXEPATH,EXEDIR,EXEFILE doesn't fit here, because I wish to copy output binary to some directory inside my project sources directory.
I.e. project resides in "f:/SOURCES/Silos" direcory.
And there is "f:/SOURCES/Silos/TEST_OUTPUT" directory where we keep a number of config files and data. So I wish that a new binary is copied there as automatic build step. The problem is TheIDE doesn't understand $(PROJECT) macro and custom post-link command cp $(EXEPATH) $(PROJECT)/TEST_OUTPUT is executed by TheIDE as cp C:\upp\out\PROJECTS\MSC9.Debug.Debug_Full.Gui.Io.Mt\Silos.exe /TEST_OUTPUT
[Updated on: Fri, 02 December 2011 12:03] Report message to a moderator
|
|
|
Re: Custom build steps upgrade [message #34627 is a reply to message #34626] |
Fri, 02 December 2011 12:55 |
|
mirek
Messages: 14039 Registered: November 2005
|
Ultimate Member |
|
|
Mindtraveller wrote on Fri, 02 December 2011 06:00 |
mirek wrote on Fri, 02 December 2011 13:13 | What about EXEPATH, EXEDIR, EXEFILE instead?
OUT* is tied to "current file", which is problem for "phony" filename...
|
If I understand you correctly, EXEPATH,EXEDIR,EXEFILE doesn't fit here, because I wish to copy output binary to some directory inside my project sources directory.
|
Ah, I see, sorry. For me it is from project to output binary dir...
I guess there is a little problem, as there can be more than single assembly. But perhaps a macro for FIRST assembly folder would do?
Mirek
|
|
|
Re: Custom build steps upgrade [message #34632 is a reply to message #34627] |
Fri, 02 December 2011 15:41 |
Mindtraveller
Messages: 917 Registered: August 2007 Location: Russia, Moscow rgn.
|
Experienced Contributor |
|
|
I'm not sure if I correctly understand what these assemblies (you mentioned in this context) are. You mean the package with custom build steps may be included into multiple assemblies? If so, then, no problem, the desired macro should define root directory of package sources, it is the same regardless the assembly. Even better approach is to add macro defining root directory for current main package sources.
[Updated on: Fri, 02 December 2011 23:11] Report message to a moderator
|
|
|
|
|
|
|
Goto Forum:
Current Time: Fri Sep 20 10:15:04 CEST 2024
Total time taken to generate the page: 0.03203 seconds
|