Recent changes to OWLMaker_3175

OWLMaker_3175 modified by Vidar Hasfjord

Vidar Hasfjord — Fri, 07 Jan 2022 12:55:10 -0000

--- v6
+++ v7
@@ -80,7 +80,9 @@

 OWLMaker will only display the options that are applicable to the version of OWLNext you are building and the tools you use to build. Click on the items to display information about each module and build mode. Use the context menu (right-click) in the list to choose default settings or quickly set or clear all checkmarks.

-Note that you must select at least one option in each build mode group for the Next button to become available. 
+However, note that the CoolPrj module does not support Unicode, so Unicode build configurations will not be generated for this module, even if the CoolPrj module and the Unicode character set mode are both selected.
+
+Also note that you must select at least one option in each build mode group for the Next button to become available. 

 *Trouble-shooting*: If the Next button stays disabled whatever you do, try to select "Select default" from the context menu (right-click) in the list.

OWLMaker_3175 modified by Vidar Hasfjord

Vidar Hasfjord — Mon, 17 Feb 2020 00:04:34 -0000

--- v5
+++ v6
@@ -1,7 +1,7 @@
 # OWLMaker Build 3175

 
- 
+ 

 OWLMaker is primarily a GUI front-end to the OWLNext build scripts. It lets the user configure and build all the OWLNext libraries in a quick and simple way.

OWLMaker_3175 modified by Vidar Hasfjord

Vidar Hasfjord — Mon, 26 Aug 2019 18:21:44 -0000

--- v4
+++ v5
@@ -43,7 +43,7 @@
 ---
 ## Preparing the OWLNext source code

-Before you can use OWLMaker, you of course need the OWLNext source code to build. See our [Installation Guide](Installing_OWLNext_from_the_Code_Repository) for more information and step-by-step instructions on how to obtain the source code and set up an OWLNext root folder for the version of OWLNext that you want to build. 
+Before you can use OWLMaker, you of course need the OWLNext source code to build. See our [Installation Guide](Installing_OWLNext) for more information and step-by-step instructions on how to obtain the source code and set up an OWLNext root folder for the version of OWLNext that you want to build. 

 ---
 ## Using the OWLMaker Wizard (Build 3175)
@@ -124,7 +124,7 @@

 Perform build setup
 
-This option performs automatic build setup. If selected, OWLMaker will pass "SETUP=1" to the build scripts causing automatic build setup to be performed. For more information about build setup, see "Perform build setup" in the OWLNext installation guide. 
+This option performs automatic build setup. If selected, OWLMaker will pass "SETUP=1" to the build scripts causing automatic build setup to be performed. For more information about build setup, see "Perform build setup" in the OWLNext installation guide. 
 

 Delete intermediate files and old targets before build

OWLMaker_3175 modified by Vidar Hasfjord

Vidar Hasfjord — Wed, 01 May 2019 14:41:22 -0000

--- v3
+++ v4
@@ -31,14 +31,14 @@
 ---
 ## Requirements

+OWLMaker Build 3175 can only build OWLNext 6.20 to 6.32. If you need to build a later version of OWLNext,  use the latest version of OWLMaker described on page "[OWLMaker](OWLMaker)".
+
 OWLMaker Build 3175 requires Windows XP or later to run.
-
-Note that OWLMaker Build 3175 should only be used if you need to build OWLNext 6.20 to 6.32. To build later versions of OWLNext, use the latest version of OWLMaker described on page "[OWLMaker](OWLMaker)".

 ---
 ## Installation

-You can find a copy of OWLMaker Build 3175 in our [Files](http://sourceforge.net/projects/owlnext/files/tools) download area. To install it, simply download the compressed package ("OWLMaker-Build-3175-for-OWLNext-6.20-to-6.32.zip"), unpack it into a writable location, and run the extracted program. 
+You can find a copy of OWLMaker Build 3175 in the "obsolete" folder in our [Files](http://sourceforge.net/projects/owlnext/files/obsolete) download area. To install it, simply download the compressed package ("OWLMaker-Build-3175-for-OWLNext-6.20-to-6.32.zip"), unpack it into a writable location, and run the extracted program. 

 ---
 ## Preparing the OWLNext source code

OWLMaker_3175 modified by Vidar Hasfjord

Vidar Hasfjord — Fri, 17 Mar 2017 07:12:10 -0000

--- v2
+++ v3
@@ -47,8 +47,6 @@

 ---
 ## Using the OWLMaker Wizard (Build 3175)
-
-**Note**: This section describes an older version of OWLMaker. Only use this version if you need to build a version of OWLNext older than 6.34. For 6.34 and later use the latest build of OWLMaker as described on page "[OWLMaker](OWLMaker)".

 To start configuring the build, select "File | OWLMaker Wizard", or simply click on the corresponding button on the toolbar.

OWLMaker_3175 modified by Vidar Hasfjord

Vidar Hasfjord — Fri, 17 Mar 2017 07:10:58 -0000

--- v1
+++ v2
@@ -38,7 +38,7 @@
 ---
 ## Installation

-You can find the latest release of OWLMaker in our [Files](http://sourceforge.net/projects/owlnext/files/tools) download area. To install it, simply download the compressed package, unpack it into a writable location, and run the extracted program. 
+You can find a copy of OWLMaker Build 3175 in our [Files](http://sourceforge.net/projects/owlnext/files/tools) download area. To install it, simply download the compressed package ("OWLMaker-Build-3175-for-OWLNext-6.20-to-6.32.zip"), unpack it into a writable location, and run the extracted program. 

 ---
 ## Preparing the OWLNext source code

OWLMaker_3175 modified by Vidar Hasfjord

Vidar Hasfjord — Fri, 17 Mar 2017 06:52:12 -0000

OWLMaker Build 3175

OWLMaker is primarily a GUI front-end to the OWLNext build scripts. It lets the user configure and build all the OWLNext libraries in a quick and simple way.

Build features:

Supports the whole range of compilers for OWLNext.
Displays the output and summary of the build process.
Filters and displays error and warning messages.
Can build multiple libraries in succession.
Allows easy selection of different build settings.

Additional features:

Integrates Yura's CoolEdit so that source and make files can be edited.
Integrates a function for converting Borland RC files to the Microsoft format.

OWLMaker is itself an OWLNext application using many of the library features. For more information about the internals of the program, see Examples.

OWLMaker Build 3175

Requirements

OWLMaker Build 3175 requires Windows XP or later to run.

Note that OWLMaker Build 3175 should only be used if you need to build OWLNext 6.20 to 6.32. To build later versions of OWLNext, use the latest version of OWLMaker described on page "OWLMaker".

Installation

You can find the latest release of OWLMaker in our Files download area. To install it, simply download the compressed package, unpack it into a writable location, and run the extracted program.

Preparing the OWLNext source code

Before you can use OWLMaker, you of course need the OWLNext source code to build. See our Installation Guide for more information and step-by-step instructions on how to obtain the source code and set up an OWLNext root folder for the version of OWLNext that you want to build.

Using the OWLMaker Wizard (Build 3175)

Note: This section describes an older version of OWLMaker. Only use this version if you need to build a version of OWLNext older than 6.34. For 6.34 and later use the latest build of OWLMaker as described on page "OWLMaker".

To start configuring the build, select "File | OWLMaker Wizard", or simply click on the corresponding button on the toolbar.

Page 1: OWLMaker Wizard main page

Enter or locate the root folder of OWLNext and click Next. The selected folder will be examined to confirm that it contains a supported version of OWLNext. An error will be shown if it does not.

If you started OWLMaker in administrator mode, then you will also have a button on this page to update the OWLROOT system environment variable. This button will be grey if the currently specified root is the same as the OWLROOT setting.

Page 2: Select build tools

Select which product will be used to build OWLNext and click Next.

Note that OWLMaker intelligently displays only the supported development tools for the detected OWLNext version in the root location specified on the previous page. The detected version is given at the top of the page. Go back and change your root if the detected version is not the version you intend to build.

Page 3: Select build locations

Enter the location of the product, or use the Locate button if available (it is not available for Borland C++ 5.5). Also Select the intermediate and final output folders and click Next.

Note: Setting the intermediate and final output folders was necessary for OWLNext 6.20, since the resulting target files had the same names, regardless of the selected compiler and build modes. In OWLNext 6.30 the compiler version and build modes are included in the target file names, and different files can hence co-exist in the same folder. Therefore, we now recommend that you leave these fields empty, provided that the OWLNext root is writable. Only if the root is read-only or protected, do you need to set these fields.

For more information, see OWLNext Naming Convention.

Page 4: Select modules and build modes

Select the combination of libraries and build modes that you want to build.

OWLMaker will only display the options that are applicable to the version of OWLNext you are building and the tools you use to build. Click on the items to display information about each module and build mode. Use the context menu (right-click) in the list to choose default settings or quickly set or clear all checkmarks.

Note that you must select at least one option in each build mode group for the Next button to become available.

Trouble-shooting: If the Next button stays disabled whatever you do, try to select "Select default" from the context menu (right-click) in the list.

Page 5: Select custom build options

Warning: Do not change anything on this page, unless you fully understand the effects it will have on the binary compatibility of the resulting libraries.

One exception to this warning is custom options that do not affect the binary output. Here are some that may be useful:

OPT="/MP": The /MP option for Visual C++ 2008 and later versions enables concurrent compilation. This can greatly speed up the build on multi-core and multi-processor systems.

Page 6: Select build tool options

Compile assembler files: This option only applies to older versions of the library. The newer versions of OWLNext no longer use assembly code. Note that you need to have an assembler installed to use this option.
Cross-compile 64-bit targets: Cross-compilation for 64-bit targets must be selected if you do not run on a 64-bit system or you do not have the native 64-bit compiler installed. This option is only available when you selected the x86-64 build mode previously.
Use incremental linker: The incremental linker is not recommended for Borland C++ 5.01/5.02. Borland C++ 5.5, C++ Builder 6.0 and Borland Developer Studio 2006 have only the incremental linker ILINK32, so if the option is unchecked, ILINK32 will be used, but with a flag to not create state files ("*.il?").
Use library sectioning: Library sectioning only applies to older Borland C++ and C++Builder compilers that do not support fine-grained function-level linking. Turning it off may speed up the build, but increases the size of the library and applications linked to it. Note that since OWLNext 6.34 library sectioning is no longer supported.
Perform build setup: This option performs automatic build setup. If selected, OWLMaker will pass "SETUP=1" to the build scripts causing automatic build setup to be performed. For more information about build setup, see "Perform build setup" in the OWLNext installation guide.
Delete intermediate files and old targets before build: This option will force a full rebuild of the library. This is similar to a make file "clean" command.
Delete intermediate files after successful build: This option will clean the "*.obj" and other intermediate files after successful build in order to free disk space.
Continue on failed builds: When you use this option, the batch will not stop even if a particular module or build mode produces build errors. This is mostly useful for developers that run build tests. A released build should normally build without errors.

Page 7: Confirm configurations and start the build process

The last page shows the commands that will be executed and the resulting libraries that will be built. Select Back to make any changes. If all is well, then click Finish to start the build process.

Build process and results

The build executes in a separate command window. After it finishes, the build output, warnings, errors and resulting target files, with build status and timing, will be shown in the Build Output window inside OWLMaker.

Use the toolbar to navigate between errors. You can double-click a warning or error message to open the associated file in the integrated editor.

Note: If you close the command window during the build, you will not only interrupt the build, but close OWLMaker altogether. If so, just reopen OWLMaker. The wizard remembers most of your settings between executions. Also note that you can minimize the windows during a long build, although it may take a few seconds before the main window reacts.

Tip: If you want to customise the command window, you can do so by pausing the build (with the command window active, press Pause on your keyboard). Then open the Properties dialog of the command window (right click on the window title bar to bring up the system menu, then select Properties). You can here enlarge the window, change window colours, select your preferred font and size, and adjust the position of the window.

Converting Borland resource files

The Microsoft resource script format (RC) does not support in-lined bitmaps (see Convert Borland C++ Resource Files to Visual C++). In the Borland resource script format, a bitmap resource can be embedded within the resource script, encoded as a hexadecimal stream, whereas in the Microsoft format the script must reference an external bitmap file.

To help you convert your Borland RC files to the Microsoft format, OWLMaker integrates a function for extracting in-lined resource bitmaps from Borland RC files. This function will create an external file for each in-lined bitmap, icon and cursor found in the specified file.

Usage:

Select Tools | Extract resource bitmaps.
Select the Borland-style resource file you want to convert.
Specify the output folder for the bitmaps.
Press Extract.

If the conversion succeeds without errors, a list of the created bitmap files will be shown in the message window, and the converted resource file will be loaded in the editor.