User forums > Help

Replacing compiler settings with a build script?

(1/7) > >>

colin:
Our company is using Python to check out files from svn and compile in a single step, which also provides arguments for selecting linux destop or a cross-compiler target.
I need to be able to disable Code::Blocks from trying to use GCC or any other compiler and just execute the company script to build the executable target.

I don't want Code::Blocks to use any compiler or makefile but just run the script, put the output into the Build log window and know where the target executable is for debugging, which does currently work when I run the script via a pre-step.
Everything I've tried from saying (*no compiler*) to clearing out makefile settings has failed.

Is there any way to do this?

stahta01:
Have you tried setting the "Build Target" to command only?

Edit:
Project -> Properties
Tab "Build Target"
Type: "command only"

Tim S.

oBFusCATed:
Do
1. Project -> Properties -> This is a custom Makefile -> check it
2. Project -> Build options -> Make commands -> edit the commands for build/clean/rebuild

colin:
Thanks for quick reply, I have tried both of these options but Code::Blocks still tries to use gcc to compile each file, even with a custom makefile.
It would seem the option (*no compiler*) is less than useless as it doesnt allow a build when set.

Also the Build log window no longer produces any output until the whole process is complete, and as a complete build could take 30 minutes that's not particularly helpful.

Is there any way to get the output window to produce anything with custom make so I can debug and see what is going on?

oBFusCATed:
Do you see your python script being executed in the log?
If not then you've not setup custom makefile!

Navigation

[0] Message Index

[#] Next page