CompileHelper 2.0: Difference between revisions

From FSDeveloper Wiki
Jump to navigationJump to search
(New page: On scenery design forums you often find questions from people who have problems with compiling their XML files or changed ASM source files. Common complaints are that a black windowed flas...)
 
No edit summary
Line 1: Line 1:
On scenery design forums you often find questions from people who have problems with compiling their XML files or changed ASM source files. Common complaints are that a black windowed
Compiling source files for Flight Simulator is something that is quite a hurdle for some users. An often heard complaint on the forums is that BGLComp or BGLC only flash shortly with a black window, but no output is being created. This happens when the user simply drops his source file on the compiler.
flashed shortly after they dropped their source file on the compiler, but no BGL or MDL file shows.


This little tool has been designed to help in the compilation process. When you drop the source file you want to compile (either ASM or XML) on CompileHelper, the output of the
In most of these cases the compiler is trying to tell the user about something that went wrong, for example a syntax error in the source file. But the compilers have been designed as command prompt applications and therefore do not support drag and drop operations.
compiler will be captured and shown to you. So when an error occurs during the compilation you will be able to see it and hopefully solve it.


[[Image:ch_errorlog.jpg]]
CompileHelper has been made to solve these problems. If you drop your source files on CompileHelper it will call the compiler for you in the background. And the output of the compiler will be presented to you in a dialog. This way you don't have to work with the command prompt yourself. So let's see how it works.


The first time you drop a source file on CompileHelper you will be asked to enter the path to the compiler (either BGLC, BGLC_9 or BGLComp). When you drop an ASM file on CompileHelper it will also detect if this file is from the Fs2002 or the Fs2004 gamepack. If it is from the Fs2004 gamepack, a MDL file will be created instead of a BGL file (this is also a common error that happens when you drop an ASM file on BGLC_9).
== Installation ==


When you accidentally drop the _0.asm file of GMax on CompileHelper it will also warn you, as you need to compile the other AMS file GMax created.
Just unzip the file you downloaded to a folder of your choice. That's all! For ease of use you might want to put a shortcut to CompileHelper on your desktop.


[[Image:ch_options.jpg]]
== Usage ==


To install this little tool, just unzip it to a folder of your choice. In this same folder an INI file will also be created to store the paths to the compilers. To make it easier to drop your source files, you could for example make a shortcut to CompileHelper on your desktop or in the folder where you keep your source files.
All you need to do is drop your source file on CompileHelper or on a shortcut that points to the tool. If you have not specified the path to the compiler needed for the source file before, you will get the options dialog where you can specify it (see below for details). Else the compiler will start and soon you will get a dialog with the messages from the compiler. So if there is an error during the compilation you will be able to see it.
 
[[Image:ch2_outputlog.jpg]]
 
If you accidentially drop the _0 ASM file or drop a fil
 
== Options ==
 
If you start CompilerHelper by double clicking on the executable or if you dropped a source file on it that does not have the compiler path specified you will get the options dialog. In this dialog you can specify the paths to the following compilers that are supported:
 
* BGLC_9
* BGLComp for FS2004
* BGLComp for FSX
* SCASM
 
There is also an option to determine whether XML files are compiled with the FS2004 or FSX BGLComp.
 
[[Image:ch2_options.jpg]]


== Support and feedback ==
== Support and feedback ==


If you have problems, questions or suggestions about CompileHelper, please let me know. You can reach me either by [mailto:arno@scenerydesign.org email] or through the forums of my website [http://www.fsdeveloper.com FsDeveloper.com].
If you have problems, questions or suggestions about CompileHelper, please [http://www.fsdeveloper.com/forum/member.php?u=1 contact me]. Or drop a message on the [http://www.fsdeveloper.com/forum/forumdisplay.php?f=23 FSDeveloper forums].


== Users license ==
== Users license ==


(c) 2005-2006 SceneryDesign.org / Arno Gerretsen
(c) 2009 SceneryDesign.org / Arno Gerretsen


This software program is distributed without charge to other scenery designers, redistribution of the program is allowed.
This software program is distributed without charge to other scenery designers, redistribution of the program is allowed.

Revision as of 13:40, 18 October 2009

Compiling source files for Flight Simulator is something that is quite a hurdle for some users. An often heard complaint on the forums is that BGLComp or BGLC only flash shortly with a black window, but no output is being created. This happens when the user simply drops his source file on the compiler.

In most of these cases the compiler is trying to tell the user about something that went wrong, for example a syntax error in the source file. But the compilers have been designed as command prompt applications and therefore do not support drag and drop operations.

CompileHelper has been made to solve these problems. If you drop your source files on CompileHelper it will call the compiler for you in the background. And the output of the compiler will be presented to you in a dialog. This way you don't have to work with the command prompt yourself. So let's see how it works.

Installation

Just unzip the file you downloaded to a folder of your choice. That's all! For ease of use you might want to put a shortcut to CompileHelper on your desktop.

Usage

All you need to do is drop your source file on CompileHelper or on a shortcut that points to the tool. If you have not specified the path to the compiler needed for the source file before, you will get the options dialog where you can specify it (see below for details). Else the compiler will start and soon you will get a dialog with the messages from the compiler. So if there is an error during the compilation you will be able to see it.

If you accidentially drop the _0 ASM file or drop a fil

Options

If you start CompilerHelper by double clicking on the executable or if you dropped a source file on it that does not have the compiler path specified you will get the options dialog. In this dialog you can specify the paths to the following compilers that are supported:

  • BGLC_9
  • BGLComp for FS2004
  • BGLComp for FSX
  • SCASM

There is also an option to determine whether XML files are compiled with the FS2004 or FSX BGLComp.

Support and feedback

If you have problems, questions or suggestions about CompileHelper, please contact me. Or drop a message on the FSDeveloper forums.

Users license

(c) 2009 SceneryDesign.org / Arno Gerretsen

This software program is distributed without charge to other scenery designers, redistribution of the program is allowed.

The copyright and any intellectual property relating to this program remain the property of the author.

The software distributed in this way may represent work in progress, and bears no warranty, either expressed or implied.