Command Line Compiling / Building

Version independent discussion forum
james.ward

Command Line Compiling / Building

Post by james.ward » 26 Feb 2008, 10:41

Hello there, we are currently working with Team Developer 3 and I was wondering, is there a way that you can compile and build a .exe using Team Developer from the command line without having to go into the development environment itself? If anyone knows a way it would be a great help.

Cheers,

James.

Jeff Luther

Command Line Compiling / Building

Post by Jeff Luther » 26 Feb 2008, 17:46

Yep, here's the list (as far as I know) in an email msg. on the gupta NG back a couple years:

Gupta Online Help: command line arguments - Gupta

-b, -B Compile and save the application as an executable file. For
example: -b myapp.app myapp.exe
The second name is optional; if omitted, the output file has the root name
of the input file with an *.EXE extension. If you do not specify a complete
path, SQLWindows puts the output file in the current working directory.

-c, -C Save an *.APT application as a normal (binary) file and exit.
This switch takes only one argument: the name of the input file with an
optional path. SQLWindows ignores any other arguments. If you do not specify
a complete path, SQLWindows puts the output file in the current working
directory.

-e -E Start SQLWindows in debug mode. When you exit the application,
SQLWindows exits (contrast this behavior with the -r switch). This switch
takes as arguments the name of the application followed by any optional
parameters you want to pass to the application.

-i, -I Edit an include library. For example:-I mylib.apl

-m, -M Generate a dynalib (.APD) and exit. This example generates a
dynalib named myapp.apd: -m myapp.apl This switch takes only one argument: the
name of the input file with an optional path. SQLWindows ignores any other
arguments. If you do not specify a complete path, SQLWindows puts the output
file in the current working directory.

-r, -R Start SQLWindows in debug mode. When you exit the application,
SQLWindows continues to run (contrast this behavior with the -e switch).
This switch takes as arguments the name of the application followed by any
optional parameters you want to pass to the application.

-x, -X Exit Windows when done. For example:-bx myapp.apt

james.ward

Command Line Compiling / Building

Post by james.ward » 26 Feb 2008, 17:51

Thanks very much Jeff, much appreciated!

cdo

Command Line Compiling / Building

Post by cdo » 20 Jul 2016, 09:55

Hi!

It can happen that compiling / building causes message boxes. Can they be suppressed somehow?

Can be reproduced by following these steps:
1. Create a Quit.app (save as [Text *.apt])
2. Go to 'Global Declarations' > 'Application Actions' and add 'On SAM_AppStartup' with Call SalQuit ( )
3. Add another line ('Ins' key) and write some invalid code like 'abc' and click enter.
4. In the upcoming message box ([comment item], [delete item], [resume editing]) click [delete item]
5. Save (a new empty line is saved in the source code)
--> closing and re-opening the file causes a message box, something like:

Code: Select all

Line 271: This item type is not allowed here.
.head 4-
The same message box opens when using cbi60.exe -B Quit.app Quit.exe
This stops our build process as nobody will ever click this message box.

Do you know a workaround for that problem?

Return to “General Discussion”

Who is online

Users browsing this forum: [Ccbot], mbonato and 0 guests