Skip to main content

Executable Specific

These macros apply only to targets declared with gpStartExecutable(). Calling them inside a module or plugin definition has no effect.

GUI executables on Windows​

gpSetGuiExecutable()

On Windows, marks the executable as a GUI application. This sets WIN32_EXECUTABLE=ON, which causes the linker to expect WinMain as the entry point rather than main and suppresses the console window on launch.

gpStartExecutable("editor")
  gpSetGuiExecutable()
  gpAddDependency(PUBLIC core)
gpEndExecutable()

On platforms other than Windows, this call has no effect.

note

If you use a compatibility shim that provides a standard main() entry point, you will still need gpSetGuiExecutable() to suppress the console window.

Custom entry point​

gpSetEntryPoint(file)

Designates a specific source file as the entry point for the executable. This is useful when the entry point is not auto-discovered by the standard directory layout, or when you want to keep it explicit and separate from the rest of the module's sources.

gpStartExecutable("launcher")
  gpSetEntryPoint(private/LauncherMain.cpp)
gpEndExecutable()

The path is relative to the target directory unless it is absolute.

Resource files​

gpAddResourceFile(file)

Adds a platform resource file to the executable. On Windows this is typically a .rc file that embeds the application icon, version information, and manifest.

gpStartExecutable("editor")
  gpAddResourceFile(resources/Editor.rc)
gpEndExecutable()

On platforms that don't use resource files, this call has no effect.

gpStartExecutable("editor")
  gpSetGuiExecutable()
  gpSetEntryPoint(private/EditorMain.cpp)
  gpAddResourceFile(resources/Editor.rc)
  gpAddDependency(PUBLIC core)
  gpAddDependency(PRIVATE gp::thirdparty::nlohmann_json)
gpEndExecutable()