User forums > Help
problem Custom command
Profic:
I have no need for this, but have some ideas :)
It seems that to make all people happier we need four separate command boxes. Two for build command and two for compile command.
And in addition it seems there is need for checkbox for selection order of them (Then build target is updated that execute first - post-build or post-compile?)
That's my two cents :)
tiwag:
--- Quote from: mandrav ---...solutions:
[*]Put a checkbox at the commands page, indicating if we want them to be executed every time or not[/list:u]
...
--- End quote ---
i think the majority of needs can be managed with that,
if one needs aditional pre-/post- compile-/link- stage commands,
it can easily be done by adding dummy targets pre-/post- added
to the very target and checking the checkbox'es accordingly.
i hope you can understand what i mean
Targets:
...
XYZ_pre_compile_always_done_commands
XYZ_pre_compile_commands
XYZ_target <<< here is the real compiled code xyz.cpp,...
XYZ post_link_commands
XYZ post_link_always_done_commands
...
--tiwag
mandrav:
I thought it over and I just made it run the steps no matter what.
It seems that most people like it this way.
On to more important matters now :)
Yiannis.
Urxae:
--- Quote ---I thought it over and I just made it run the steps no matter what.
It seems that most people like it this way.
--- End quote ---
Please don't do that, because if these commands return error codes, the build fails.
For example: when I compile .dlls, I usually have it generate the .a files as well, and in post-build commands move these to the lib/ subdirectory. When I build the entire project and the dll doesn't need to be relinked, that move command will halt the build for no good reason.
mandrav:
--- Quote ---...that move command will halt the build for no good reason.
--- End quote ---
Do you care to elaborate?
Why would it halt the build? What kind of error might be raised?
Yiannis.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version