Hi Grey / Iarwain,
Is there much of a chance of getting a template for VS2010 Express or more hopefully, a tutorial on getting SVN compiled under CodeLite for windows?
I have been trying it and I was stuck at the OpenAL / dsound.h issue again (like for VS2005 a while back). I resolved that with the DirectX SDK include path but now compiling gives an issue with a missing SAL.h.
There are profiles for Embedded Windows Debug in the OpenAL solution so I'm sure it's been done before.
Thanks, guys, not prepared to shell out thousands for Visual Studio and I'm not a student so I think it's going to be CodeLite for me going forward.
Well for vs2010, I'm out of the loop, I'm still using vs2008 so only Grey can help you with that.
As for CodeLite, which version of mingw did you install? You should have dsound.h in your mingw/include folder. It's probably not exactly the same version as your DX SDK one so pointing to it will have unpredictable results.
In order to use CodeLite on windows all you need is a recent version of MinGW (gcc needs to be at least version 4.5.0 and gcc 4.4.x won't create objects that are binary compatible with gcc 4.5.x).
I'll get the latest and try those other suggestions. I'll report back.
There should already be a compiled version in openal-soft/lib/mingw that should work with your new version of gcc. Unless 4.6.1 isn't compatible with the object made with 4.5.0, again.
I'll have a look at the tutorials now how to get a working project to replace my vs2005 one.
I'm also using pretty old versions of codelite/mingw so I'll try to update tonight and try again.
This is codelite 3.0 from the website and the latest mingw from mingw.org.
But I have been trying to find a download for mingw 4.5.x but it's not so simple to find from their site.
I managed to set up a codelite solution for my project and I had a few compiler specific problems there but from what I read, there are problems with 4.6.x. So I am pretty keen to downgrade to whatever specific version you have there.
As for mingw, I think that you can think older packages from their custom installer but I'm not 100% sure.
This link seems to indicate a version download if the local xml file is edited. Not sure how simple / straight forward this is.
I finally found a spot on the MingW site that would allow a version to download with GCC 4.5.2-1 (close enough?), from here: http://www.mingw.org/wiki/InstallationHOWTOforMinGW
There were manual instructions and the links here have the 4.5.2-1 version of GCC.
I got the latest SVN and loaded the workspace at codeuildcodeliteorx.workspace
Right clicked the orx parent node and selected Build Workspace.
It went a lot further than GCC 4.6.1 but this time a lot of errors regarding:
So I think I'm closer but something still isn't right. How did you go with CodeLite 3.0 & latest MingW? Maybe I am still missing a step.
Here is the last few lines:
The best way to verify is to check the content of /code/lib/dynamic. If you find there liborx.a/orx.dll and the other variants, you're all set.
PS: Actually I think the "Not Compiled" name is the config name I gave for a "nothing to do" as CodeLite doesn't allow to cherry pick with projects will be compiled for which configuration (as Visual Studio does), so instead of creating 2 separate workspaces, I just created a configuration that does nothing for a project when it's not needed (ie. the plugins in embedded mode).
Seems I am all good to go. I guess the GCC 4.5.2 fixes this though I should go and check with the original 4.6.1 setup but I'm not game to break anything now.
Thanks again for your help. Tutorial examples build and run from codelite but not my project, that is something I need to sort out myself.
I'll report that as bug bug to the CodeLite team.
Glad to report that my project is up and running nicely under codelite, so I am back to normal business.
By the way, you might find compiling orx-dev-mingw-1.3rc0.zip interesting with the new toolchain. I found this failed too with something regarding a missing malloc.c but I didn't want to cloud this thread. Just wanted to let you know.
Ok, so the log when compiling the workspace:
I'll try this out with codelite and confirm all is fine.