Ninja generator bug

[alex-rass-88]

What seems to be the problem?
If the workspace and projects are in different directories, then the Ninja generator incorrectly generates commands for postbuild, prebuild and prelink.

What did you expect to happen?
Ninja handles commands from subninja differently than make does. They are treated as if they are in the same directory as the main ninja.build.

What version of Premake are you using?
9af00b1

The solution to the problem:
in modules/ninja/ninja_cpp.lua in functions m.buildPreBuildEvents, m.buildPreLinkEvents and m.buildPostBuildEvents replace project location to workspace location for translateCommandsAndPaths:

local commands = os.translateCommandsAndPaths(cfg.prelinkcommands, cfg.project.basedir, cfg.project.location) => local commands = os.translateCommandsAndPaths(cfg.prelinkcommands, cfg.project.basedir, cfg.workspace.location)

[nickclark2016]

I think I built this with the "VS" like behavior in mind. If you're dependent on a specific file location, I'd definitely recommend using tokens instead of trying to manually put in absolute paths. For example, if you need something project location relative, you can use:

prelinkcommands "%{!prj.location}/some_binary"

https://premake.github.io/docs/Tokens/

I personally use this approach for dealing with any time I'm dealing with the file system in the custom build events. If this isn't sufficient, let me know and I can take a look at figuring out a more uniform way to deal with this.

[alex-rass-88]

Good. I have worked with many build systems. Writing postbuild rules and the like is always a pain. Everything works fine when they're not there.