<include file="presets/wx.bkl"/>
- <exe id="minimal" template="wx">
- <app-type>gui</app-type>
+ <exe id="minimal" template="wxgui">
<debug-info>on</debug-info>
<runtime-libs>dynamic</runtime-libs>
To simplify the building of wxWidgets-based projects, wxWidgets contains a
set of Bakefiles that automatically configure your build system to be
compatible with wxWidgets. As you'll notice in the sample above, the sample
-project uses the wx template. Once you've included the template, your software
-will now build with wxWidgets support.
+project uses the "wxgui" template. Once you've included the template, your software
+will now build as a GUI application with wxWidgets support.
+
+There's also "wxconsole" template for building console-based wxWidgets applications
+and "wx" template that doesn't specify application type (GUI or console) and can be
+used e.g. for building libraries that use wxWidgets.
But since the wx presets don't exist in the Bakefile presets subfolder,
Bakefile needs to know where to find these presets. The "-I" command adds the
<debug-info>$(_DEBUGINFO)</debug-info>
</if>
</template>
+
+ <!-- Template for building wx-based GUI applications -->
+ <template id="wxgui" template="wx">
+ <app-type>gui</app-type>
+ </template>
<!-- Template for building wx-based console applications -->
<template id="wxconsole" template="wx">
- <define>wxUSE_GUI=0</define>
<app-type>console</app-type>
</template>
<include file="presets/wx.bkl"/>
- <exe id="minimal" template="wx">
- <app-type>gui</app-type>
+ <exe id="minimal" template="wxgui">
<!-- this sample builds always in debug mode; if you have
compiled wxWidgets in release mode, you'll get link errors! -->