premake change

[Geoff Evans]

Heads up: I just changed premake so it will vomit sln and vcproj (and make) files into the location of premake4.lua (the root and Dependencies folders).  They used to go into a Premake/ folder.

I did this because it makes developing with SublimeText easier, which is turn make life waaaaay better on Mac and Linux (a focus of mine for the time being).

Oh, and heads up: the platform abstraction layer (besides realtime timers) now works on mac using Clang, linux using Gcc, as well as windows using Cl.  Woohoo!

I don't expect Foundation to be too much trouble for Mac, and my end goal is to get Reflect building on all three soon (since I want to put them to work in other places).

Also, Clang is awesome!

[Li YG]

I am using SublimeText and the project files are generated in the sub folder build directory, it works quite well by setting working_dir. even with sublimegdb, it also works well by settting sublimegdb_workingdir.

don't know what is the reason to block you using the sub folder?

--
You received this message because you are subscribed to the Google Groups "Helium" group.
To unsubscribe from this group and stop receiving emails from it, send an email to heliumprojec...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Geoff Evans]

The problem I run into is that the relative paths spit out by the compiler aren't relative to the location of the premake project file.  So compile errors on Platform are reported at errors in ..\Platform\ThreadPosix.cpp:500, which SublimeText can't resolve to a valid file when double clicking on the error in the build result window.

Also, I would love to use sublimegdb, but I have never been able to get it to work given the directions on the git repo.  Any tips?  I have set it up correctly, I think... and F5 puts SublimeText into debugging mode, but the debuggee never starts up and the UI remains empty.  I would *love* to get it working through.  gdb is pretty nice, but having to use it from a separate shell can get annoying sometimes.

[Li YG]

1. my setting is the .sublime-project file is at the root, while the generated make file is in the sub folder build. the make file is generated by premake

2. sublimegdb can work, but, we need to modify a bit according to:https://github.com/quarnster/SublimeGDB/issues/47

3. btw, this works perfectly for me, but, I forgot to say, it is on win7 with cygwin's gcc. 

[Geoff Evans]

I just pushed another premake change... we are back to a single, unified solution (make) file: Helium.sln.  Tools and Runtime libs are still named as appropriate, and libs that are agnostic are named Core.<name>, to differentiate them.

This was done to make it a bit easier to spot changes that break Runtime projects compiling.

Its my plan to build a CI server at my home to build everything on Mac/Win/Linux to spot build issues.