User forums > Using Code::Blocks

Compiling on a remote system (using a CB tool that runs ssh)

<< < (2/3) > >>

johanekdahl:
Solved some of the upgrade problems:

I needed to copy the share folder to
    C:\Documents and settings\myUserName\application data\codeblocks

I seem to recall that I stumble on this every time I upgrade. Absolutely nothing about this is mentioned in the post about installing a nightly ( http://forums.codeblocks.org/index.php/topic,3232.0.html ).

So now C::B start up without errors again (phew!), but I still have the old dialogue where the setting that Morten mentioned is not present. In fact, there are no tabs at all, and the only thing present in the left column is "Batch build".

johanekdahl:
Solved more of the problems: Making a new shortcut made the new correct tabbed dialogue box re-appear (no idea why...).

So now I can start tinkering with this parsing of errors. To restate, an error message looks like this:


--- Code: ---stderr> ../Frameworks/ClassLib/PropertyLib/PropertyContainer.cpp:283: error: `unlnk' undeclared (first use this function)
--- End code ---

Note that the makefile is not at the root of the source/project tree. This is necessary as we are building for several different targets ("production build" for the actual target, "unit test build" targteted/executed at the same system as the build is taking place on, etc. All of those builds have their own configurations so we cannot let the build spread over the source tree.) This is why the error starts with "../" .

So now I have this regexp:

--- Code: ---stderr> \.\./([][{}() \t#%$~A-Za-z0-9_:+/\.-]+):([0-9]+):[ \t](.*)
--- End code ---

and it does not work (nothing happends when double-clicking it). Anyone spot the mistake that I am blind for?

And to re-iterate: Tools have their outputs go to the Code::Blocks tab (NOT the "Build messages" tab) in the Messages window. Is this tab really sensitive to double-clicks?

(If the answer is actually yes, then would you suspect that Alt-F2 also works? My speculation is that both the double-clicking and Alt-F2 works only in the "Build messages" tab.)

johanekdahl:
Mario!

Took another look at Uniwin. It seems to me that it is intended for having the "original" source tree on the Windows system. Uniwin will then "synch" a that tree with a copy on the Linux system where the build will take place.

I actually have the original tree on the Linux system.

Running Uniwin would synch a tree that is actually on the Linux system with a copy that is also on the Linux system. We are talking about a few thousand source files (.cpp and .h), that has to be synched generating network traffic over my Windoze system.

I also could not find out how to direct Uniwin to use a certain toolchain on the Linux system (yes there are several toolchains present, and I suspect that the Linux-gurus have tweaked the configure-scripts to use the correct one for building for the real target or building for unit tests etc). Come to think of it, isn't it so that you actually will be using C::B's internal build system rather than anexternal makefile. If so then Uniwin is definitely out, as there are loads of specialities in our makefiles. Building with them is an absolute must!

johanekdahl:
So, anyone have an answer for my first question: Is there any way to get C::B to save all files before running a tool?

rickg22:
johanekdahl:

Right idea, wrong tool.

Instead of configuring a tool, you should define a new compiler. This way you can compile with your remote compiler. The custom compiler setup is just like "tools", except it has a different command line for compiling, linking, etc.

Navigation

[0] Message Index

[#] Next page

[*] Previous page