Opened 5 years ago

Last modified 17 months ago

#1518 new task

Submit premake modifications to upstream

Reported by: leper Owned by:
Priority: Nice to Have Milestone: Backlog
Component: Build & Packages Keywords:
Cc: Yves, fabio Patch:

Description (last modified by leper)

We bundle a modified version of premake 4.3 to create our workspaces (VS projects, makefiles, ...).

Some of our modifications are bug fixes (relative paths, precompiled headers), enhancements (cxxtest support, nasm support) or extensions to upstream features (os_getversion support for POSIX sytems (os_getversion is a backport from premake-4.4-beta4)).

It would be nice to

  • submit these modifications to upstream by adding a pull request there. See the premake contribution guidelines for information on how to submit patches.
  • add diff/patch files and a readme describing the use of the modification to the premake dir (analogous to how we handle nvtt modifications). (could be useful for the first task)

The attached file is a diff against the imported premake version (see link above) before r11970.

Attachments (1)

0ad_premake.diff (24.4 KB) - added by leper 5 years ago.

Download all attachments as: .zip

Change History (15)

Changed 5 years ago by leper

Attachment: 0ad_premake.diff added

comment:1 Changed 5 years ago by leper

Cc: Yves added

CCing Yves as he did most of the changes to premake.

comment:2 Changed 5 years ago by leper

I added a pull request with our additions to getversion() upstream

comment:3 Changed 5 years ago by fabio

Cc: fabio added

comment:4 Changed 5 years ago by leper

The pull request hasn't been merged, but a slightly modified version of it has been committed to premake-dev and premake-stable (which will become 4.4).

We still need to adjust our local version to be the same as the code upstream, but that shouldn't be hard to do.

Last edited 5 years ago by leper (previous) (diff)

comment:5 Changed 5 years ago by fabio

Ideally there should be also a configure option for using system premake, similar to nvtt/mozjs/enet.

comment:6 Changed 5 years ago by leper

Description: modified (diff)

This is sort of the reason for this ticket (and to keep us from having to maintain a fork), but we depend on some of the modifications and I don't know (for all of them) wether they are still used/needed or if they should just be dropped. (I added Yves to cc some time ago as he did most of those changes afaik)

Also premake-dev (which will become 5.0) changes a lot of the api so we will probably have to do some work once that is released (or hits beta).

And just that I mentioned it here #1516 should probably be fixed properly and submitted too..

comment:7 Changed 5 years ago by leper

In 12903:

Sync with upstream. Refs #1518.

comment:8 Changed 4 years ago by leper

In 13512:

Use os.findlib to find boost. Patch by Markus. Fixes #1938. Refs #1518.

comment:9 Changed 4 years ago by leper

r13512 imports upstream pull request #7 and modifies it a bit to handle case of a missing /etc/ gracefully (happens on BSDs). Also imports os.is64bit(), but strips the native code implementation, as that only works on windows currently and isn't needed at the moment.

comment:10 Changed 4 years ago by leper

Bugfix to parse_ld_so_conf was merged upstream.

comment:11 Changed 4 years ago by leper

r13901 added a NoDebugHeap? flag.

comment:12 Changed 4 years ago by leper

r13970 and r14111 for VS2012 and VS2013 support.

comment:13 Changed 18 months ago by Itms

Premake5 is actively being developed, and they are not likely to keep maintaining the 4.x branch much longer. I created a new ticket for the migration: #3729.

On top of that, they migrated to GitHub so most of the links here are broken.

Leaving this ticket open sounds sensible because the list of customizations is useful, but basically we should focus on a migration more than on 4.x IMO.

comment:14 Changed 17 months ago by Zsolt Dollenstein

In light of that, we should probably just apply the patch from #404, since we no longer want to stay as close to 4.x upstream as possible. Wdyt?

Note: See TracTickets for help on using tickets.