User forums > Using Code::Blocks
Custom make commands are never executed
kriegaex:
I created a new project with an existing external makefile. I selected "This is a custom Makefile". I created a new target "all" to check if the external Makefile is triggered. It is.
So far, so good. Now I edited the first entry in the target's "Make commands" section. Unfortunately, this setting seems to be ignored. Whatever I write there, even something like "echo 'test'", is ignored. Pre- and post-commands are run, though.
I am a CB newbie, so maybe I am doing something wrong (if so, nothing obvious). If so, tell me what, please. Otherwise I guess this might be a bug.
I am on Ubuntu 11.10 64-bit and using the CB package which is part of the distribution.
Jenna:
If the makefile is called, then it is either a bug of make, or a miswritten makefile.
If you turn on full commandline logging for the compiler you have chosen for your project/target, you should see all the output of the make command.
See http://wiki.codeblocks.org/index.php?title=FAQ-Compiling_%28errors%29#Q:_How_do_I_troubleshoot_a_compiler_problem.3F for an instruction how to do it.
Be aware, that just the make command of the compiler is used, not the compiler itself.
kriegaex:
Maybe we have a misunderstanding here: I am using a custom makefile. It is called, but not the way I specify in the command line editor (see attached image). As you can see, I even changed the command completely for testing so as not to call make at all, but echo some text to the console, but my command line is not used - against my expectation. CB always calls "make <target>" no matter what I specify in custom commands.
Edit: OMG, I guess CB is quite buggy in the version (svn 7671) offered by Ubuntu 11.10:
* When I switch on "Compiler logging" - "Full command line", suddenly my custom command sudo -A $make -f $makefile $target is called and executed successfully. Besides, I have also specified a global variable SUDO_ASKPASS (with value /usr/lib/openssh/gnome-ssh-askpass) via "Settings" - "Global variables" so as to enable my make command to run in sudo environment and ask me for a password via GUI. But as soon as I set my logging options back to "task description" instead of "full command line", my commandline is completely ignored again! This is definitely a bug, and a big one.
* When I re-enter "Settings" - "Global variables" to check my previous variable settings, suddenly SUDO_ASKPASS is printed in lower-case letters as sudo_askpass. It is still used correctly by the custom command line, though. Another bug.
* My custom "make install" ends successfully with 1 warning and 0 errors, but CB prints the opposite: 0 warnings, 1 error, which is definitely wrong. The same false information is shown in "Build log" window and in "Build messages"
Guys, I have just created my first project and run my first make, but already discovered three easy to spot bugs at once. I must say, I am shocked. Anyway, I would like to continue testing CB because it starts up faster and seems leaner on my old machine than Eclipse, but I do hope you have some solutions or bugfixes for me. Are these known bugs which are fixed in newer versions? If so, please try to trigger the maintainers of the Ubuntu/Debian packages and urge them to upgrade to a newer release. The way it is now, the software is absolutely useless, not even able to run an external makefile with a custom command without a trick (turning on full command line logging).
MortenMacFly:
This is your first post...
--- Quote from: kriegaex on March 11, 2012, 01:30:19 pm ---Guys, I have just created my first project and run my first make, but already discovered three easy to spot bugs at once. I must say, I am shocked.
--- End quote ---
[...]
--- Quote from: kriegaex on March 11, 2012, 01:30:19 pm ---but I do hope you have some solutions or bugfixes for me.
--- End quote ---
I have to say you have a strange attitude.
Sure - all bugs must be on our side and surely we will serve you at will. What else can we do for you? Do you like a beer, an ice-cream and a massage, too?
kriegaex:
Look, I am a user and a CB newbie, but not stupid and a computer scientist and developer like many of you here, too. CB is neither my first IDE nor is this my first Linux build. I usually use the command line, so I know how to call and debug make. I also know how to do what I want with Eclipse.
What I want is just to be taken seriously, not a beer and definitely not a massage. Would you not agree that the three issues I have mentioned are bugs? I have posted twice now, but my first post has not been taken seriously and not read thoroughly. I told you what was wrong and I got an irrelevant reply. No problem, misunderstandings happen every day. So I tried to make myself understood by posting a reply with more details and even a screenshot to clarify things. And what do I get as a reply now? A polemic, sarcastic comment and again no relevant answer.
Hey, bugs are a normal thing, but would you not be shocked if at first contact with a new IDE with an everyday core task (building a program) you would not just bump into one, but into three errors at once? Many people would immediately give up and go back to what they know is working, never touching the software again, free or not. I am different and stated clearly that I want to keep testing, I just needed help and was even suggesting the bugs might be old and already fixed, blaming Ubuntu package maintainers for not upgrading their package.
Sure, to say that I am shocked is a personal statement, but one backed by facts (three reproduceable bugs, I can create a screen cam for you if you like). I insulted noone and said clearly what I want from you: hints, bugfixes, help. And you just insult me personally instead of offering help. Is this how you welcome new users?
Edit and P.S.: I am not just demanding something, I am not a leecher. I took the time to report three errors. So first I was giving away something: my time and devotion as a free tester for your project. I have led an OSS project long enough to know that this is important. Software development is for users, but also the developers cannot improve a lot without feedback. I just gave feedback, and this is what I get in return. Thank you so much.
Navigation
[0] Message Index
[#] Next page
Go to full version