User forums > Using Code::Blocks
Problem creating same output as VS 2005
TDragon:
--- Quote from: yamokosk on June 21, 2007, 10:39:54 pm ---Is there any way to capture the command terminal steps of both programs? So I can see what is actually being passed to cl.exe by VS and cl.exe by C::B?
--- End quote ---
VS2005 generally creates a build log in the intermediate files directory called BuildLog.htm. In Code::Blocks, you can see the full command line in the Build Log window by changing the Compiler logging option in Settings->Compiler and debugger->Global compiler settings->Other settings to "Full command line".
Edit: Beatz0r'ed. :P
MortenMacFly:
--- Quote from: yamokosk on June 21, 2007, 10:39:54 pm ---Is there any way to capture the command terminal steps of both programs? So I can see what is actually being passed to cl.exe by VS and cl.exe by C::B?
--- End quote ---
In Matlab there is a verbose switch (or similar) for the compiler... I don't recall exactly - but I can have a look when I'm at work if you like. For C::B have a look at my sig. It will tell you what to do... ;-)
And yes: If the command line produced by C::B is the same and the one from Matlab AND the path settings are correct (e.g. consider environment variables, too maybe) then it *will* produce identical output (besides date stamps maybe). For sure.
With regards, Morten.
MortenMacFly:
--- Quote from: TDragon on June 21, 2007, 10:49:40 pm ---VS2005 generally creates a build log in the intermediate files directory called BuildLog.htm.
--- End quote ---
I believe he isn't compiling in VC2005 but in Matlab - but even there *could* be created a build log... if it is setup (which is the default IMHO).
With regards, Morten.
yamokosk:
I am moving from VS to C::B.. well to be more specific it was more like Matlab > VS > C::B. Just to review, I can compile and run mex files from VS with no problems. Its only when I try and do the same thing in C::B that I am running into trouble.
At any rate, I found that build log produced by VS (I wish it was more of an integrated option like it is for C::B..). But at any rate, I will pour over the two logs to see whats missing or not getting included.
MortenMacFly:
--- Quote from: yamokosk on June 21, 2007, 10:59:42 pm ---Just to review, I can compile and run mex files from VS with no problems.
--- End quote ---
Oh! Ok... this was my misunderstanding. I though you only use the compiler of VS2005 but compile inside Matlab. (I always did that.) Ok then... probably in this case the batch file from Matlab is incorrect. Make sure you do a "mex -setup" before (on the Matlab prompt) and configure Matlab appropriately for the VC compiler. But you can also parse the log... this should contain the most important information, too.
With regards, Morten.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version