Shuffling project between OSs

[kencamargo]

Hello,

Is there an easy way to transport a project back and forth between Linux and win environments? What I have done so far is to generate an empty project on one side and copy the source files from the other, but this becomes a little impractical as projects grow in complexity, and the wxSmith GUI files are not automatically added to the project.

Any thoughts are appreciated.

Thanks in advance,
Ken

[koso]

I am using the same project files in Linux and Windows and have no problems so far. You haven't written, why you cant do it this way so it is difficult to help. When there are different paths in your environments, you can use global variables...

[frithjofh]

Hi,

if I recall correctly there is a thread in the forum dealing with cross compilation issues. I could imagine you should find some useful ideas there too, as it seems the topics are a bit related.

Regards

frithjofh

[kencamargo]

I am using the same project files in Linux and Windows and have no problems so far. You haven't written, why you cant do it this way so it is difficult to help. When there are different paths in your environments, you can use global variables...

Under win, you have a long list of libraries and paths; under Linux code::blocks uses the wx-config route, which is far simpler. AFAIK this is not available under win.

[kencamargo]

if I recall correctly there is a thread in the forum dealing with cross compilation issues. I could imagine you should find some useful ideas there too, as it seems the topics are a bit related.

Hi there,
Nope, not exactly cross-compiling. That much I'm comfortable with. The problem is that I have one specific app that shows a crazy bug when cross-compiled (under Linux for win x86), which goes away when compiled under win (on a VM, which is a different beast from cross-compilation). In this particular case I have to migrate a project accross OSs, not cross-compile to one target OS from another host OS.
But thanks anyway.
Ken

[Jenna]

You can create different targets for windows and linux and keep them in the same project-file (and/or workspace).

[kencamargo]

You can create different targets for windows and linux and keep them in the same project-file (and/or workspace).

I know, Jens, I've been doing that for a while now, using your instructions and packages (thank you, btw). The issue here is that I have one specific project that has a problem when I do the cross build under Linux, so I have to take the whole thing to a Win vm, and I can't simply take the same project; as I wrote elsewhere, under Linux the wx-config script is used (even for the cross-compiling), that is not the case under Win. Or am I missing something?

Ken

[stahta01]

For an wx-config under windows see http://sites.google.com/site/wxconfig/
Note, I do not think that will solve your problem; but, it might help.

Tim S.

[kencamargo]

For an wx-config under windows see http://sites.google.com/site/wxconfig/
Note, I do not think that will solve your problem; but, it might help.

Tim S.

Thanks Tim, this will certainly help, even if it doesn't solve everything.

Ken

[dmoore]

You can create different targets for windows and linux and keep them in the same project-file (and/or workspace).

I know, Jens, I've been doing that for a while now, using your instructions and packages (thank you, btw). The issue here is that I have one specific project that has a problem when I do the cross build under Linux, so I have to take the whole thing to a Win vm, and I can't simply take the same project; as I wrote elsewhere, under Linux the wx-config script is used (even for the cross-compiling), that is not the case under Win. Or am I missing something?

If you have win32 and linux targets in your project you can specify compiler and link options for each target (the lib list for win32, wx-config for linux). Why doesn't this work for you?