Before opening a new bug report, please read Reporting Bugs and consider if this is something you can contribute yourself. If this a new bug, help us help you by filling in the template below.

What seems to be the problem?
When a person uses a path name to a project on linux that contains a space, the build process fails. We noticed the generated Makefiles do not account for the spaces in the paths and the build process will throw an error. Below is a santised generated Makefile command.

Linking foo.plugin^M
g++ -o "../../../linux-x86_64/foo.plugin.so" -L"/home/user/project name/release" -L/usr/lib64 -Wl,-rpath=/home/user/project name/release/python/lib -lpython3.11
g++: error: name/release/python/lib: No such file or directory
make[1]: *** [Makefile:102: ../../../linux-x86_64/foo.plugin.so] Error 1

What did you expect to happen?
I would have expected the generated Makefiles would account for the spaces in the directory paths. I notice the -L LIBDIRS are quoted, but not the rpath.

What have you tried so far?
We are not using spaces in the directory names on linux, but we can't manage all developers local development environment.

How can we reproduce this?
I would suggest trying any project on linux, checking out the git project where the root directory has a space, like "project name".

• Visual Studio 2022 (vs2022)
• Visual Studio 2019 (vs2019)
• Visual Studio 2017 (vs2017)
• Visual Studio 2015 (vs2015)
• Visual Studio 2012 (vs2012)
• Visual Studio 2010 (vs2010)
• Visual Studio 2008 (vs2008)
• Visual Studio 2005 (vs2005)
• GNU Makefile (gmake)
• GNU Makefile Legacy (gmakelegacy)
• XCode (xcode)
• Codelite
• Other (Please list below)

What version of Premake are you using?
5.0.0-beta2