Several Tundra2 betas have been around for a while now and today I pushed a new and better Codelite exporter for Tundra2 to my github repository.
Tundra was developed by game developers and primarily for game developers:
- fast, especially for incremental builds
- reliable incremental builds
- no guessing: compiler, paths and libs must be known
- uses multiple cores
help request:
I couldn't test the generator on Windows so if any Windows user wants to give Tundra a try get my exporter and let me know if and where it fails (I got a hunch...)
To test Tundra on Windows you can either use an installer (64bit Windows only) or you can build it yourself (unfortunately there's only a VS2012 sln for Windows).
I'd do it myself but my Windows is still 32bit so the installer doesn't work and I don't have enough free disc space for VS 2012 (b/c it insists on dumping >2GB somewhere on drive C: )
I don't have a Mac either so if someone would give it a try on OSX and let me know in case of any problems that'd be nice (I assume it just works, though)
One thing has been bugging me ever since I wrote that first generator:
In a project's configuration, does Codelite expect certain strings as CompilerType and DebuggerType? If so, could I get a list of the valid ones?
Code: Select all
<Configuration Name="Foo" CompilerType="gnu gcc" DebuggerType="GNU gdb debugger" Type="Executable" BuildCmpWithGlobalSettings="append" BuildLnkWithGlobalSettings="append" BuildResWithGlobalSettings="append">
For now the generator seems to do everything I need it to do but there are some TODOs left in the code, among them one about the debugger section and one about code completion. Anyone running into problems there please point me in the right direction (or fix it yourself and send me a pull request)
As with all open source code (or so I hope) constructive criticism is always welcome