Overview
Examples
Screenshots
Comparisons
Applications
Download
Documentation
Tutorials
Bazaar
Status & Roadmap
FAQ
Authors & License
Forums
Funding Ultimate++
Search on this site
Search in forums












SourceForge.net Logo
Home » Community » U++ community news and announcements » Custom build steps upgrade
Re: Custom build steps upgrade [message #34626 is a reply to message #34624] Fri, 02 December 2011 12:00 Go to previous messageGo to previous message
Mindtraveller is currently offline  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

 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: CParser::GetSpacePtr
Next Topic: Sql::SetSession, Sql0
Goto Forum:
  


Current Time: Fri May 17 01:27:11 CEST 2024

Total time taken to generate the page: 0.01547 seconds