-
If you enable the "no-exceptions" build flag in a premake project, the setting is ignored for VS200x and C++ exceptions are still enabled.
Behavior confirmed with VS2005 and VS2008.
The attached patch will fix this.
2008-08-10 19:10:32 UTC in Premake
-
Agreed, this is more of a "known issue" than a bug, I reported it purely for tracking purposes.
I ended up writing a Lua function in a common premake file to set the post-build steps, fixing the paths if necessary.
This function also allowed me to solve another issue referencing different target paths per config in the post-build steps (e.g. "../bin/Debug/foo" and "../bin/Release/foo").
2007-06-12 00:10:13 UTC in Premake
-
When using the VS200x targets on Windows, paths in the pre/post-build commands are not converted to their native form (using backslashes). This prevents Visual Studio from successfully launching the commands.
This seems to be the only part of Visual Studio which doesn't understand Unix paths (unfortunately).
For now you must use a conditionnal block in your premake file:
if windows then.
2007-06-10 15:41:33 UTC in Premake
-
Here's a patch that fixes this. GNU target now uses the proper set of pre/post commands based on the selected config.
File Added: gnu-buildsteps.diff.
2007-06-10 12:11:54 UTC in Premake
-
Xbox 360 support for premake would be really cool, but there are potential legal issues with integrating it in the official distribution.
There are different "Tools" blocks in the .vcproj that are required to build on Xbox 360, so buildoptions don't work here as premake doesn't know how to write those new blocks. It's a simple modification to make in vs.c. There also needs to be some extra...
2007-05-30 01:29:37 UTC in Premake
-
Here is a patch that adds a "vs2005-x64" target to premake. Unit tests included.
2007-05-27 20:11:40 UTC in Premake
-
The following doesn't work for the GNU target:
package.config["Debug"].postbuildcommands = { "foo" }
package.config["Release"].postbuildcommands = { "bar" }
After a "premake --target gnu" is issued, There is no sign of "foo" nor "bar" in the generated Makefile.
Other targets handle this correctly (vs6, vs2002, vs2003, vs2005, cb-gcc).
For the GNU target, the only syntax that works...
2007-05-23 00:24:20 UTC in Premake
-
Using the current CVS version, SWIG will crash using
the attached input file. I've stripped the source class
to a minimum for a repro.
This seems to be related to %ignore. If I don't %ignore
methods in the source class, no crash occurs. If I
don't enable directors, no crash occurs either.
This is on i686-pc-mingw32 with gcc-3.4.4, command line
is "swig -c++ -csharp repro.i".
2006-08-20 16:25:55 UTC in SWIG
-
fulg committed patchset 12 of module gdbstubs to the gdbstubs CVS repository, changing 1 files.
2000-11-09 23:11:04 UTC in gdbstubs
-
fulg committed patchset 11 of module gdbstubs to the gdbstubs CVS repository, changing 1 files.
2000-11-09 23:04:00 UTC in gdbstubs
