Recent changes to Installing_OWLNext

Installing_OWLNext modified by Vidar Hasfjord

Vidar Hasfjord — Sat, 01 Nov 2025 05:04:02 -0000

--- v177
+++ v178
@@ -284,7 +284,7 @@

 To link OWLNext in your own projects, you do not need to explicitly specify the OWLNext library file to the linker, since OWLNext uses [auto-linking](https://en.wikipedia.org/wiki/Auto-linking) controlled by pragma statements in the library headers. See "[include/owl/private/owllink.h](https://sourceforge.net/p/owlnext/code/6763/tree/tags/7.0.12/include/owl/private/owllink.h#l116)".

-If you are using the old Borland C++ IDE, see [FAQ](https://sourceforge.net/p/owlnext/wiki/Frequently_Asked_Questions/#how-do-i-resolve-link-errors-referring-to-bc5libowlwlib) for advise on how to turn off linking with the old OWL.
+If you are using the old Borland C++ IDE, see [FAQ](https://sourceforge.net/p/owlnext/wiki/Frequently_Asked_Questions/#how-do-i-resolve-link-errors-referring-to-bc5libowlwlib) for advice on how to turn off linking with the old OWL.

 For details on the naming of the library files, see our library file [naming convention](OWLNext_naming_convention).

Installing_OWLNext modified by Vidar Hasfjord

Vidar Hasfjord — Sat, 30 Aug 2025 12:57:48 -0000

--- v176
+++ v177
@@ -20,6 +20,19 @@
 ### Supported compiler

 To build and use OWLNext you need a compiler on our list of [Supported Compilers](Supported_Compilers). The OWLNext installation procedure is similar for all the supported compilers, and is described in the following sections.
+

+
+---
+## Quick start
+
+If you just want to get OWLNext up and running:
+
+1. Download the latest [OWLMaker](OWLMaker) from the [project home page](https://sourceforge.net/projects/owlnext).
+2. Launch OWLMaker and choose **Tools → OWLMaker Wizard**.
+
+That’s it — OWLMaker will guide you through the rest.
+
+The following sections describe the installation process and options in more detail, including troubleshooting, tips, and IDE setup.
 


 ---

Installing_OWLNext modified by Vidar Hasfjord

Vidar Hasfjord — Fri, 07 Feb 2025 04:02:53 -0000

--- v175
+++ v176
@@ -33,9 +33,9 @@
 ---
 ## Download the source code

-**Note:** We use the Subversion system for source code version control. If you are not familiar with this system and the associated terminology ("working copy", "trunk", "branches", "tags"), see the [FAQ](http://sourceforge.net/p/owlnext/wiki/Frequently_Asked_Questions/#what-do-you-mean-by-revision-trunk-branches-and-tags) for help.
-
-You have two options: Either download a static snapshot of the version of OWLNext you want, or use a [Subversion](http://subversion.apache.org) client to create a _working copy_ for one of the release branches. In the latter case, you can thereafter keep the working copy up-to-date using the Subversion commands.
+**Note:** We use the [Subversion](http://subversion.apache.org) system for source code version control. If you are not familiar with this system and the associated terminology ("working copy", "trunk", "branches", "tags"), see the [FAQ](http://sourceforge.net/p/owlnext/wiki/Frequently_Asked_Questions/#what-do-you-mean-by-revision-trunk-branches-and-tags) for help.
+
+You have two options: Either download a static snapshot of the version of OWLNext you want, or use a Subversion client to create a _working copy_ for one of the release branches. In the latter case, you can thereafter keep the working copy up-to-date using the Subversion commands.

 A third option, now obsolete, is to use the Embarcadero installer for OWLNext 6.32, which can be further upgraded to version 6.34 via patch files. However, it is outdated, and we do not recommend its use. It is only documented here for completeness.

Installing_OWLNext modified by Vidar Hasfjord

Vidar Hasfjord — Tue, 29 Oct 2024 01:51:19 -0000

--- v174
+++ v175
@@ -73,14 +73,14 @@

 To use this option, you need to first install a Subversion client, e.g. the highly recommended [TortoiseSVN](http://tortoisesvn.net/). Then use the Subversion command "svn checkout" to create a working copy. The "svn:" path for the OWLNext repository is found in the Code section. Go to the project Code section and browse to the version that you want. Here are the currently supported versions:

-  * [trunk](http://sourceforge.net/p/owlnext/code/HEAD/tree/trunk/) (OWLNext 8, prerelease)
-  * [branches/7.0](http://sourceforge.net/p/owlnext/code/HEAD/tree/branches/7.0/) (OWLNext 7.0, latest stable release) 
-  * [branches/644](http://sourceforge.net/p/owlnext/code/HEAD/tree/branches/644/) (OWLNext 6.44, [Long-Term Support](https://en.wikipedia.org/wiki/Long-term_support) release) 
+  * [trunk](http://sourceforge.net/p/owlnext/code/HEAD/tree/trunk) (OWLNext 8, prerelease)
+  * [branches/7](http://sourceforge.net/p/owlnext/code/HEAD/tree/branches/7) (OWLNext 7.0, latest stable release) 
+  * [branches/6.44](http://sourceforge.net/p/owlnext/code/HEAD/tree/branches/6.44) (OWLNext 6.44, [Long-Term Support](https://en.wikipedia.org/wiki/Long-term_support) release) 

  Simply concatenate the repository path and the path to the selected branch or tag. For example, to check out the 7.0 branch into the folder "C:\OWLNext" the command will be:

 ~~~~bat
-svn checkout svn://svn.code.sf.net/p/owlnext/code/branches/7.0 C:\OWLNext
+svn checkout svn://svn.code.sf.net/p/owlnext/code/branches/7 C:\OWLNext
 ~~~~

 If you use TortoiseSVN, just right-click the folder you prepared earlier and select "SVN Checkout". Specify the "svn:" address to the selected branch or tag, and press OK. TortoiseSVN will then download the files into your folder.

Installing_OWLNext modified by Vidar Hasfjord

Vidar Hasfjord — Wed, 27 Dec 2023 12:45:59 -0000

--- v173
+++ v174
@@ -241,16 +241,6 @@
 


 ---
-## Link the libraries
-
-To link OWLNext in your own projects, you do not need to explicitly specify the OWLNext library file to the linker, since OWLNext uses [auto-linking](https://en.wikipedia.org/wiki/Auto-linking) controlled by pragma statements in the library headers. See "[include/owl/private/owllink.h](https://sourceforge.net/p/owlnext/code/6763/tree/tags/7.0.12/include/owl/private/owllink.h#l116)".
-
-If you are using the old Borland C++ IDE, see [FAQ](https://sourceforge.net/p/owlnext/wiki/Frequently_Asked_Questions/#how-do-i-resolve-link-errors-referring-to-bc5libowlwlib) for advise on how to turn off linking with the old OWL.
-
-For details on the naming of the library files, see our library file [naming convention](OWLNext_naming_convention).
-

-
----
 ## Test the installation

 To test that everything is set up correctly, you may want to build and run the example projects provided in the examples folder created by the installation. See [Examples](Examples) for an overview of some of the available examples.
@@ -277,6 +267,16 @@
 


 ---
+## Link the libraries
+
+To link OWLNext in your own projects, you do not need to explicitly specify the OWLNext library file to the linker, since OWLNext uses [auto-linking](https://en.wikipedia.org/wiki/Auto-linking) controlled by pragma statements in the library headers. See "[include/owl/private/owllink.h](https://sourceforge.net/p/owlnext/code/6763/tree/tags/7.0.12/include/owl/private/owllink.h#l116)".
+
+If you are using the old Borland C++ IDE, see [FAQ](https://sourceforge.net/p/owlnext/wiki/Frequently_Asked_Questions/#how-do-i-resolve-link-errors-referring-to-bc5libowlwlib) for advise on how to turn off linking with the old OWL.
+
+For details on the naming of the library files, see our library file [naming convention](OWLNext_naming_convention).
+

+
+---
 ## Get the OWLNext API documentation

 You can access the online [OWLNext API Documentation](http://owlnext.sourceforge.net/help/html/index.html) from the wiki [Main Page](Main_Page). Alternatively, you can look for an offline help file in our [Files](http://sourceforge.net/projects/owlnext/files/) download area. If you cannot find the version that you want, you may build the documentation yourself from the source using [Doxygen](http://www.doxygen.org). See the Doxygen documentation for details.

Installing_OWLNext modified by Vidar Hasfjord

Vidar Hasfjord — Wed, 27 Dec 2023 12:34:49 -0000

--- v172
+++ v173
@@ -243,7 +243,7 @@
 ---
 ## Link the libraries

-To link OWLNext in your own projects, you do not need to explicitly specify the OWLNext library file to the linker, since OWLNext uses auto-linking controlled by pragma statements in the library headers. See "[include/owl/private/owllink.h](https://sourceforge.net/p/owlnext/code/6763/tree/tags/7.0.12/include/owl/private/owllink.h#l116)".
+To link OWLNext in your own projects, you do not need to explicitly specify the OWLNext library file to the linker, since OWLNext uses [auto-linking](https://en.wikipedia.org/wiki/Auto-linking) controlled by pragma statements in the library headers. See "[include/owl/private/owllink.h](https://sourceforge.net/p/owlnext/code/6763/tree/tags/7.0.12/include/owl/private/owllink.h#l116)".

 If you are using the old Borland C++ IDE, see [FAQ](https://sourceforge.net/p/owlnext/wiki/Frequently_Asked_Questions/#how-do-i-resolve-link-errors-referring-to-bc5libowlwlib) for advise on how to turn off linking with the old OWL.

Installing_OWLNext modified by Vidar Hasfjord

Vidar Hasfjord — Wed, 27 Dec 2023 12:33:07 -0000

--- v171
+++ v172
@@ -241,6 +241,16 @@
 


 ---
+## Link the libraries
+
+To link OWLNext in your own projects, you do not need to explicitly specify the OWLNext library file to the linker, since OWLNext uses auto-linking controlled by pragma statements in the library headers. See "[include/owl/private/owllink.h](https://sourceforge.net/p/owlnext/code/6763/tree/tags/7.0.12/include/owl/private/owllink.h#l116)".
+
+If you are using the old Borland C++ IDE, see [FAQ](https://sourceforge.net/p/owlnext/wiki/Frequently_Asked_Questions/#how-do-i-resolve-link-errors-referring-to-bc5libowlwlib) for advise on how to turn off linking with the old OWL.
+
+For details on the naming of the library files, see our library file [naming convention](OWLNext_naming_convention).
+

+
+---
 ## Test the installation

 To test that everything is set up correctly, you may want to build and run the example projects provided in the examples folder created by the installation. See [Examples](Examples) for an overview of some of the available examples.

Installing_OWLNext modified by Vidar Hasfjord

Vidar Hasfjord — Tue, 29 Aug 2023 12:22:44 -0000

--- v170
+++ v171
@@ -168,7 +168,7 @@
 

 ### Prepare your build tools

-Make sure that your compiler installation have all the libraries necessary, such as the Windows SDK, set up and ready. In particular, some versions of OWLNext require the Boost library to compile with Embarcadero C++Builder/RAD Studio, and Boost may not be installed by default. If it is not, go to the GetIt Plugin Manager within the IDE and install it.
+Make sure that your compiler installation have all the libraries necessary, such as the Windows SDK, set up and ready. In particular, some versions of OWLNext require the Boost library to compile with Embarcadero C++Builder/RAD Studio, and Boost may not be installed by default. If it is not, go to the GetIt Plugin Manager within the IDE and install it. Make sure that the installation path agrees with CG_BOOST_ROOT in the make-files, otherwise you will get compilation errors (see [bugs:#549]).

 **Note about legacy toolsets**: Some legacy toolsets, such as Borland C++ and Embarcadero's legacy toolset (BCC32), may require that support for short filenames (8.3 format aliases) is enabled for the disk volume on which the toolset is installed. Otherwise, the OWLNext build may fail. In modern Windows, short filename support is only enabled for the system drive (usually "C:") by default. Hence, we recommend installing your build tools on the system drive in the default location (usually within "C:\\Program Files" or "C:\\Program Files (x86)").

Installing_OWLNext modified by Vidar Hasfjord

Vidar Hasfjord — Thu, 29 Dec 2022 03:26:55 -0000

--- v169
+++ v170
@@ -73,9 +73,9 @@

 To use this option, you need to first install a Subversion client, e.g. the highly recommended [TortoiseSVN](http://tortoisesvn.net/). Then use the Subversion command "svn checkout" to create a working copy. The "svn:" path for the OWLNext repository is found in the Code section. Go to the project Code section and browse to the version that you want. Here are the currently supported versions:

-  * [trunk](http://sourceforge.net/p/owlnext/code/HEAD/tree/trunk/) (Prerelease)
-  * [branches/7.0](http://sourceforge.net/p/owlnext/code/HEAD/tree/branches/7.0/) (OWLNext 7.0, latest development release) 
-  * [branches/644](http://sourceforge.net/p/owlnext/code/HEAD/tree/branches/644/) (OWLNext 6.44, latest stable release) 
+  * [trunk](http://sourceforge.net/p/owlnext/code/HEAD/tree/trunk/) (OWLNext 8, prerelease)
+  * [branches/7.0](http://sourceforge.net/p/owlnext/code/HEAD/tree/branches/7.0/) (OWLNext 7.0, latest stable release) 
+  * [branches/644](http://sourceforge.net/p/owlnext/code/HEAD/tree/branches/644/) (OWLNext 6.44, [Long-Term Support](https://en.wikipedia.org/wiki/Long-term_support) release) 

  Simply concatenate the repository path and the path to the selected branch or tag. For example, to check out the 7.0 branch into the folder "C:\OWLNext" the command will be:

Installing_OWLNext modified by Vidar Hasfjord

Vidar Hasfjord — Thu, 21 Jul 2022 23:32:05 -0000

--- v168
+++ v169
@@ -269,4 +269,4 @@
 ---
 ## Get the OWLNext API documentation

-You can access the online [OWLNext API Documentation](http://owlnext.sourceforge.net/help/html/index.html) from the wiki [Main Page](Main_Page). Alternatively, you can look for an offline help file in our [Files](http://sourceforge.net/projects/owlnext/files/) download area. If you cannot find an updated version, you may build the documentation yourself from the source using [Doxygen](http://www.doxygen.org). See the Doxygen documentation for details.
+You can access the online [OWLNext API Documentation](http://owlnext.sourceforge.net/help/html/index.html) from the wiki [Main Page](Main_Page). Alternatively, you can look for an offline help file in our [Files](http://sourceforge.net/projects/owlnext/files/) download area. If you cannot find the version that you want, you may build the documentation yourself from the source using [Doxygen](http://www.doxygen.org). See the Doxygen documentation for details.