Compiling XWP - Revision history

Ak120 at 04:16, 20 November 2018

2018-11-20T04:16:22Z

← Older revision		Revision as of 06:16, 20 November 2018
Line 18:		Line 18:
	2) Create a subdirectory in your CVS root directory named "xworkplace" (e.g. x:\cvs\xworkplace), change to this subdirectory.		2) Create a subdirectory in your CVS root directory named "xworkplace" (e.g. x:\cvs\xworkplace), change to this subdirectory.

	3) If this is first time you have used the XWP Sources ~~respository~~, you need to log in. Do:		3) If this is first time you have used the XWP Sources repository, you need to log in. Do:

	SET USER=guest		SET USER=guest
Line 41:		Line 41:
	2) Create a subdirectory in your CVS root directory named "xwphelpers" (e.g. x:\cvs\xwphelpers), change to this subdirectory.		2) Create a subdirectory in your CVS root directory named "xwphelpers" (e.g. x:\cvs\xwphelpers), change to this subdirectory.

	3) If this is first time you have used the XWP Sources ~~respository~~, you need to log in. Do:		3) If this is first time you have used the XWP Sources repository, you need to log in. Do:

	SET USER=guest		SET USER=guest
Line 96:		Line 96:
	cvs upd		cvs upd

	in each subdirectory to be updated. It is safe to use this command even if you have changes in progress. Cvs will not overwrite your ~~uncommited~~ changes.		in each subdirectory to be updated. It is safe to use this command even if you have changes in progress. Cvs will not overwrite your uncommitted changes.

	When working with an existing sandbox, there's no need to set CVSROOT or USER. Cvs records this data in control files within the sandbox.		When working with an existing sandbox, there's no need to set CVSROOT or USER. Cvs records this data in control files within the sandbox.

Martini: /* Compiling the beast */

2012-03-14T21:12:40Z

Compiling the beast

← Older revision		Revision as of 23:12, 14 March 2012
Line 136:		Line 136:

	1) first of all, adjust x:\CVS\xworkplace\config.in to your needs;		1) first of all, adjust x:\CVS\xworkplace\config.in to your needs;

	2) then, from x:\CVS\xworkplace\ run		2) then, from x:\CVS\xworkplace\ run

Andib: /* Compiling the beast */

2009-10-17T18:10:05Z

Compiling the beast

← Older revision		Revision as of 20:10, 17 October 2009
Line 117:		Line 117:
	== Compiling the beast ==		== Compiling the beast ==

	* IBM VisualAge C++ 3.0 with fixpak 8 is recommended (and it is also the only environment currently supported.		* IBM VisualAge C++ 3.0 with fixpak 8 is recommended (and it is also the only environment currently supported). VAC3.65 can be used for multi-threaded widgets and to build a multi-threading helpers36.lib
	* OS/2 Developer's Toolkit for all the SOM header files and the SOM compiler: the ones included in eCS 1.2 CD #2 seems good. If you are using some other Toolkit, be sure to backlevel emitc.dll to the OS/2 Warp 4.0 Toolkit version.		* OS/2 Developer's Toolkit for all the SOM header files and the SOM compiler: the ones included in eCS 1.2 CD #2 seems good. If you are using some other Toolkit, be sure to backlevel emitc.dll to the OS/2 Warp 4.0 Toolkit version.
	* Several versions of rc.exe are around, and not all of them work well for XWP compilation. Good versions are for sure:		* Several versions of rc.exe are around, and not all of them work well for XWP compilation. Good versions are for sure:

Ggamba: /* Branch, trunk, tags... */ Updated to 1.08

2008-06-11T20:42:01Z

Branch, trunk, tags...: Updated to 1.08

← Older revision		Revision as of 22:42, 11 June 2008
Line 78:		Line 78:
	in the XWP sources and the XWP helpers sandbox directories.		in the XWP sources and the XWP helpers sandbox directories.

	To checkout '''version 1.0.7''' (the latest released version):		To checkout XWP '''version 1.0.8''' (the latest released version):

	cvs checkout -r ~~pr_0005_1~~-0-7 .		cvs checkout -r pr_0006_1-0-8 .

	in the XWP sources ~~directory and~~		in the XWP sources directory.

	~~cvs checkout -r pr_0016_xwp1-0-7 .~~

	~~in the XWP helpers~~ directory.

	Once you have done an initial checkout from CVS, you can use the ''cvs status -v filename'' command to determine which tags exist. For example, run:		Once you have done an initial checkout from CVS, you can use the ''cvs status -v filename'' command to determine which tags exist. For example, run:
Line 94:		Line 90:
	from the x:\cvs\xworkplace directory to see the existing tags for the XWorkplace package. This works because the developers always tag makefile for every release even if this file has not changed.		from the x:\cvs\xworkplace directory to see the existing tags for the XWorkplace package. This works because the developers always tag makefile for every release even if this file has not changed.

	All the above samples are for an ~~intiial~~ checkout from the CVS server. This means that you are downloading from CVS into an empty directory.		All the above samples are for an initial checkout from the CVS server. This means that you are downloading from CVS into an empty directory.

	Once you have done an initial checkout of a branch or the trunk, you usually want to use the "update" command to download files modified by others instead of the "checkout" command. The update command is faster than the checkout command because it generally does a lot less work. Run the command:		Once you have done an initial checkout of a branch or the trunk, you usually want to use the "update" command to download files modified by others instead of the "checkout" command. The update command is faster than the checkout command because it generally does a lot less work. Run the command:

Ggamba: /* Compiling the beast */

2007-12-19T19:52:27Z

Compiling the beast

← Older revision		Revision as of 21:52, 19 December 2007
Line 152:		Line 152:
	You have also good chance to get an error like:		You have also good chance to get an error like:

	E:\netlabs_CVS\xworkplace\bin\modules\xwphook.dll => E:\programs\xworkplace\~~binxwphook~~.dll		E:\netlabs_CVS\xworkplace\bin\modules\xwphook.dll => E:\programs\xworkplace\bin\xwphook.dll
	SYS0032: Process can't access file...		SYS0032: Process can't access file...

	This means that you have XWorkplace running and you have to ~~UNLOCK~~ the files first if you are copying over your running files. ~~Put~~ XWP_UNLOCK_MODULES = YES in CONFIG.IN~~. It~~'s down near the bottom. The Unlock utility from the LxLite package is required.		This means that you have XWorkplace running and you have to '''unlock''' the files first if you are copying over your running files. Check that XWP_UNLOCK_MODULES = YES line exists in CONFIG.IN (it's down near the bottom). The Unlock utility from the LxLite package is required. If XWP_UNLOCK_MODULES should not be enough, manually unlock XWPHOOK.DLL and XWPDAEMN.EXE.

	==Notes for contributors==		==Notes for contributors==

Ggamba: /* Compiling the beast */

2007-12-19T19:47:06Z

Compiling the beast

← Older revision		Revision as of 21:47, 19 December 2007
Line 148:		Line 148:
	3) After that, run either "nmake all" or "nmake really_all". "nmake all" will only rebuild XFLDR.DLL, XWPDAEMN.EXE and XWPHOOK.DLL while "nmake really_all" will produce the full set of XWorkplace executables plus the NLS files.		3) After that, run either "nmake all" or "nmake really_all". "nmake all" will only rebuild XFLDR.DLL, XWPDAEMN.EXE and XWPHOOK.DLL while "nmake really_all" will produce the full set of XWorkplace executables plus the NLS files.

	In case of problems, verify ~~that~~ x:\CVS\xworkplace\bin\full directory has been created. If not, create it.		In case of problems, verify if x:\CVS\xworkplace\bin\full directory has been created. If not, create it.

	You have also good chance to get an error like:		You have also good chance to get an error like:

Ggamba: /* Compiling the beast */

2007-12-19T11:42:21Z

Compiling the beast

← Older revision		Revision as of 13:42, 19 December 2007
Line 148:		Line 148:
	3) After that, run either "nmake all" or "nmake really_all". "nmake all" will only rebuild XFLDR.DLL, XWPDAEMN.EXE and XWPHOOK.DLL while "nmake really_all" will produce the full set of XWorkplace executables plus the NLS files.		3) After that, run either "nmake all" or "nmake really_all". "nmake all" will only rebuild XFLDR.DLL, XWPDAEMN.EXE and XWPHOOK.DLL while "nmake really_all" will produce the full set of XWorkplace executables plus the NLS files.

	In case of problems, verify that x:\CVS\xworkplace\bin\full has been created. If not, create it.		In case of problems, verify that x:\CVS\xworkplace\bin\full directory has been created. If not, create it.

	You have also good chance to get an error like:		You have also good chance to get an error like:

Ggamba: Note about creation of \bin\full directory

2007-12-19T11:41:55Z

Note about creation of \bin\full directory

← Older revision		Revision as of 13:41, 19 December 2007
Line 148:		Line 148:
	3) After that, run either "nmake all" or "nmake really_all". "nmake all" will only rebuild XFLDR.DLL, XWPDAEMN.EXE and XWPHOOK.DLL while "nmake really_all" will produce the full set of XWorkplace executables plus the NLS files.		3) After that, run either "nmake all" or "nmake really_all". "nmake all" will only rebuild XFLDR.DLL, XWPDAEMN.EXE and XWPHOOK.DLL while "nmake really_all" will produce the full set of XWorkplace executables plus the NLS files.

	You have good chance to get an error like:		In case of problems, verify that x:\CVS\xworkplace\bin\full has been created. If not, create it.

			You have also good chance to get an error like:

	E:\netlabs_CVS\xworkplace\bin\modules\xwphook.dll => E:\programs\xworkplace\binxwphook.dll		E:\netlabs_CVS\xworkplace\bin\modules\xwphook.dll => E:\programs\xworkplace\binxwphook.dll

Ggamba: Note about rc.exe

2007-03-29T09:45:15Z

Note about rc.exe

@@ Line 123: / Line 123: @@
 * IBM VisualAge C++ 3.0 with fixpak 8 is recommended (and it is also the only environment currently supported.
 * OS/2 Developer's Toolkit for all the SOM header files and the SOM compiler: the ones included in eCS 1.2 CD #2 seems good.  If you are using some other Toolkit, be sure to backlevel emitc.dll to the OS/2 Warp 4.0 Toolkit version.
 Now, you have on your computer all what is needed to compile XWP.

Ggamba: www.netlabs.org -> cvs.netlabs.org

2007-01-20T16:56:53Z

www.netlabs.org -> cvs.netlabs.org

← Older revision		Revision as of 18:56, 20 January 2007
Line 12:		Line 12:
	1) Create the CVS root folder (e.g. x:\CVS) and then do:		1) Create the CVS root folder (e.g. x:\CVS) and then do:

	SET CVSROOT=:pserver:guest@~~www~~.netlabs.org:/netlabs.cvs/xworkplace		SET CVSROOT=:pserver:guest@cvs.netlabs.org:/netlabs.cvs/xworkplace

	This is the location of the XWP Sources repository at Netlabs.		This is the location of the XWP Sources repository at Netlabs.
Line 35:		Line 35:
	1) First, do:		1) First, do:

	SET CVSROOT=:pserver:guest@~~www~~.netlabs.org:/netlabs.cvs/xwphelpers		SET CVSROOT=:pserver:guest@cvs.netlabs.org:/netlabs.cvs/xwphelpers

	This is the location of the XWP Helpers repository.		This is the location of the XWP Helpers repository.