XQilla: Linux / BSD / *nix / Cygwin Build Documentation

Most recent edit on 2009-11-16 09:05:43 by HarryLoaker [added]

Additions:
~&I intend to add some scripting to generate windows project paper writing∞ files and the Makefile.am listings from the same common list of source and headers. Until that is done, be aware that the windows project files will also need updating for added or removed source and headers.

Deletions:
~&I intend to add some scripting to generate windows project files and the Makefile.am listings from the same common list of source and headers. Until that is done, be aware that the windows project files will also need updating for added or removed source and headers.

Edited on 2009-10-14 11:47:08 by JohnSnelson [Reverted to version from 2009-01-06 13:22:48]

Additions:
Building XQilla under Cygwin follows the same steps as for other Unixes, however the default behavior is to generate only a static library. To get the shared library (and the Cygwin DLL) you need to make some changes to the generated Makefile. Open the Makefile and find the line that looks like:
To run the application you either have to do a make install on XQilla (to get the cygxqilla-0.dll on the correct directory) or copy the cygxqilla-0.dll to the same directory of the executable.

Deletions:
Building XQilla under Cygwin follows the same steps as for other Unixes, however, the default behavior is to generate only a static library. To get the shared library (and the Cygwin DLL) you need to make some changes to the generated Makefile. Open the Makefile and find the line that looks like:
To run the application you either have to do a make install on XQilla(to get the cygxqilla-0.dll on the correct directory) or copy the cygxqilla-0.dll to the same directory of the executable.

Edited on 2009-09-24 16:10:10 by MatthewWalters [Cygwin]

Additions:
Building XQilla under Cygwin follows the same steps as for other Unixes, however, the default behavior is to generate only a static library. To get the shared library (and the Cygwin DLL) you need to make some changes to the generated Makefile. Open the Makefile and find the line that looks like:
To run the application you either have to do a make install on XQilla(to get the cygxqilla-0.dll on the correct directory) or copy the cygxqilla-0.dll to the same directory of the executable.

Deletions:
Building XQilla under Cygwin follows the same steps as for other Unixes, however the default behavior is to generate only a static library. To get the shared library (and the Cygwin DLL) you need to make some changes to the generated Makefile. Open the Makefile and find the line that looks like:
To run the application you either have to do a make install on XQilla (to get the cygxqilla-0.dll on the correct directory) or copy the cygxqilla-0.dll to the same directory of the executable.

Edited on 2009-01-06 13:22:48 by JohnSnelson [XQilla builds against an install of Xerces-C now.]

Additions:
~-Make sure you have downloaded and built the Xerces-C library. It can be downloaded here∞.

Deletions:
~-Make sure you have downloaded and built the Xerces-C library. It can be downloaded here∞. Unfortunately XQilla currently needs to build against the source tree for Xerces-C, so an install of it won't do.

Edited on 2008-01-24 15:12:56 by JohnSnelson [Undo vandalism from a while ago that removed half the page]

Additions:
~&I intend to add some scripting to generate windows project files and the Makefile.am listings from the same common list of source and headers. Until that is done, be aware that the windows project files will also need updating for added or removed source and headers.

Configure Options

Specifying "--help" to the configure script will give you a list of options. When developing I usually use "--enable-debug --disable-static --disable-fast-install".

Useful Make Targets

"clean" - Removes all the executable, library and object files, and lets you build from scratch.
"docs" - Builds the doxygen documentation - you'll need Doxygen∞ installed for this.
"dist" - Rolls the distributions.
"tags" - Makes an emacs "TAGS" file from the source code.

Building from another directory

This can be useful if you want to have two builds at the same time. Often I will have a debug build and a release build. This can also be useful if you want to cross-compile for a number of platforms, or if you just want to keep the "xqilla" directory free from object files. This will only work if you're version of "make" has VPATH support - which I think means GNU make. To do this:

Create a directory for the build to go in. I usually make it inside the "xqilla" directory, but that is not mandatory.
Run the configure script from inside the new directory.
Make the project as usual form inside the new directory.

Building on Cygwin

Building XQilla under Cygwin follows the same steps as for other Unixes, however the default behavior is to generate only a static library. To get the shared library (and the Cygwin DLL) you need to make some changes to the generated Makefile. Open the Makefile and find the line that looks like:

libxqilla.la: $(libxqilla_la_OBJECTS) $(libxqilla_la_DEPENDENCIES) 
	    $(CXXLINK) -no-undefined -rpath $(libdir) $(libxqilla_la_LDFLAGS) $(libxqilla_la_OBJECTS) $(libxqilla_la_LIBADD) $(LIBS) -lxerces-c

Change it to (adding the options: -no-undefined and -lxerces-c to it):

libxqilla.la: $(libxqilla_la_OBJECTS) $(libxqilla_la_DEPENDENCIES) 
	    $(CXXLINK) -no-undefined -rpath $(libdir) $(libxqilla_la_LDFLAGS) $(libxqilla_la_OBJECTS) $(libxqilla_la_LIBADD) $(LIBS) -lxerces-c

This generates the cygxqilla-0.dll, and libxqilla.dll.a file, which is what is needed to link your code to the dynamic library. If you want to link your code to the dynamic libraries, you need to use libtool under Cygwin. Here is an example of a Makefile line that will link you objects to XQilla and Xerces under Cygwin:

$(TGT): $(OBJS)
	    libtool --tag=CXX --mode=link g++ -v -lstdc++ -lxerces-c -lxqilla  $(OBJS) -o $(TGT)

To run the application you either have to do a make install on XQilla (to get the cygxqilla-0.dll on the correct directory) or copy the cygxqilla-0.dll to the same directory of the executable.

CategoryDocumentation

Edited on 2008-01-24 15:08:00 by JohnSnelson [Mention that a source tree of Xerces-C is needed]

Additions:
~-Make sure you have downloaded and built the Xerces-C library. It can be downloaded here∞. Unfortunately XQilla currently needs to build against the source tree for Xerces-C, so an install of it won't do.

Change directory to the build directory
```
cd XQilla-1.0
```

Run the configure script

./configure --with-xerces=/path/to/xerces/source/tree

Build XQilla
```
make
```
*Optional* Install XQilla (as a super-user)
```
make install
```
Deletions:
~-Make sure you have downloaded and build the Xerces-C library. It can be downloaded here∞.
Change directory to the build directory -
```
 XQilla-1.0
```

Run the configure script -

./configure --with-xerces=/path/to/xerces

Build XQilla -
```
make
```
*Optional* Install XQilla (as a super-user) -
```
make install
```
Edited on 2007-11-22 10:34:04 by JohnSnelson [Reverted to version from 2007-05-15 07:23:53]

Deletions:
rolsitbooual

Edited on 2007-11-13 01:06:47 by VarerDaral

Additions:
rolsitbooual

Edited on 2007-05-15 07:23:53 by JohnSnelson

Additions:
~-Change directory to the build directory -
```
 XQilla-1.0
```
Deletions:
~-Change directory to the build directory - %Í XQilla-1.0%%

Edited on 2007-04-19 21:07:53 by CisA6q

Additions:
~-Change directory to the build directory - %Í XQilla-1.0%%

Deletions:
~-Change directory to the build directory -
```
cd XQilla-1.0
```
I intend to add some scripting to generate windows project files and the Makefile.am listings from the same common list of source and headers. Until that is done, be aware that the windows project files will also need updating for added or removed source and headers.

Configure Options

Specifying "--help" to the configure script will give you a list of options. When developing I usually use "--enable-debug --disable-static --disable-fast-install".

Useful Make Targets

"clean" - Removes all the executable, library and object files, and lets you build from scratch.
"docs" - Builds the doxygen documentation - you'll need Doxygen∞ installed for this.
"dist" - Rolls the distributions.
"tags" - Makes an emacs "TAGS" file from the source code.

Building from another directory

Create a directory for the build to go in. I usually make it inside the "xqilla" directory, but that is not mandatory.
Run the configure script from inside the new directory.
Make the project as usual form inside the new directory.

Building on Cygwin

libxqilla.la: $(libxqilla_la_OBJECTS) $(libxqilla_la_DEPENDENCIES) 
	    $(CXXLINK) -no-undefined -rpath $(libdir) $(libxqilla_la_LDFLAGS) $(libxqilla_la_OBJECTS) $(libxqilla_la_LIBADD) $(LIBS) -lxerces-c

Change it to (adding the options: -no-undefined and -lxerces-c to it):

libxqilla.la: $(libxqilla_la_OBJECTS) $(libxqilla_la_DEPENDENCIES) 
	    $(CXXLINK) -no-undefined -rpath $(libdir) $(libxqilla_la_LDFLAGS) $(libxqilla_la_OBJECTS) $(libxqilla_la_LIBADD) $(LIBS) -lxerces-c

$(TGT): $(OBJS)
	    libtool --tag=CXX --mode=link g++ -v -lstdc++ -lxerces-c -lxqilla  $(OBJS) -o $(TGT)

To run the application you either have to do a make install on XQilla (to get the cygxqilla-0.dll on the correct directory) or copy the cygxqilla-0.dll to the same directory of the executable.

CategoryDocumentation

Edited on 2007-01-25 03:38:29 by JohnSnelson

Additions:

Linux / BSD / *nix / Cygwin Build Documentation

Deletions:

Linux / BSD / *nix Build Documentation

Edited on 2007-01-23 13:09:19 by TmsExnebula

Additions:

Building on Cygwin

libxqilla.la: $(libxqilla_la_OBJECTS) $(libxqilla_la_DEPENDENCIES) 
	    $(CXXLINK) -no-undefined -rpath $(libdir) $(libxqilla_la_LDFLAGS) $(libxqilla_la_OBJECTS) $(libxqilla_la_LIBADD) $(LIBS) -lxerces-c

Change it to (adding the options: -no-undefined and -lxerces-c to it):

libxqilla.la: $(libxqilla_la_OBJECTS) $(libxqilla_la_DEPENDENCIES) 
	    $(CXXLINK) -no-undefined -rpath $(libdir) $(libxqilla_la_LDFLAGS) $(libxqilla_la_OBJECTS) $(libxqilla_la_LIBADD) $(LIBS) -lxerces-c

$(TGT): $(OBJS)
	    libtool --tag=CXX --mode=link g++ -v -lstdc++ -lxerces-c -lxqilla  $(OBJS) -o $(TGT)

To run the application you either have to do a make install on XQilla (to get the cygxqilla-0.dll on the correct directory) or copy the cygxqilla-0.dll to the same directory of the executable.

Edited on 2005-12-14 16:43:01 by JohnSnelson

Additions:
This can be useful if you want to have two builds at the same time. Often I will have a debug build and a release build. This can also be useful if you want to cross-compile for a number of platforms, or if you just want to keep the "xqilla" directory free from object files. This will only work if you're version of "make" has VPATH support - which I think means GNU make. To do this:

Deletions:
This can be useful if you want to have two builds at the same time. Often I will have a debug build and a release build. This can also be useful if you want to cross-compile for another platform. This will only work if you're version of "make" has VPATH support - which I think means GNU make. To do this:

Edited on 2005-12-14 16:26:55 by JohnSnelson

Additions:

CategoryDocumentation

Edited on 2005-12-14 16:20:52 by JohnSnelson

Additions:
~-Create a directory for the build to go in. I usually make it inside the "xqilla" directory, but that is not mandatory.

Run the configure script from inside the new directory.
Make the project as usual form inside the new directory.

Deletions:
~-Create a directory for the build to go in. I usually make it inside the "xqilla" directory, but that is not mandatory
Run the configure script from inside the new directory
Make the project as usual form inside the new directory

Edited on 2005-12-14 16:20:02 by JohnSnelson

Additions:

Adding / Removing Files

If you need to add/remove files from the build, it needs to be done in the Makefile.am in the "xqilla" directory, unless the files are inside the "include" directory - when they need to be put in include/Makefile.am. The Makefile has rules to automatically rebuilds itself and it's dependants if they need to be rebuilt.

Useful Make Targets

"clean" - Removes all the executable, library and object files, and lets you build from scratch.
"docs" - Builds the doxygen documentation - you'll need Doxygen∞ installed for this.
"dist" - Rolls the distributions.
"tags" - Makes an emacs "TAGS" file from the source code.

Deletions:
If you need to add/remove files from the build, it needs to be done in the Makefile.am in the "xqilla" directory, unless the files are inside the "include" directory - when they need to be put in include/Makefile.am.

Edited on 2005-12-14 16:09:31 by JohnSnelson

Additions:
~&I intend to add some scripting to generate windows project files and the Makefile.am listings from the same common list of source and headers. Until that is done, be aware that the windows project files will also need updating for added or removed source and headers.

Edited on 2005-12-14 16:06:47 by JohnSnelson

Additions:
The build system uses autoconf, automake and libtool. It is set to build (mostly) from a single Makefile in the "xqilla" directory. There is a sub-directory Makefile in the "include" directory, but I only did that because I couldn't get the headers to install to the correct path otherwise.

Configure Options

Specifying "--help" to the configure script will give you a list of options. When developing I usually use "--enable-debug --disable-static --disable-fast-install".

Building from another directory

This can be useful if you want to have two builds at the same time. Often I will have a debug build and a release build. This can also be useful if you want to cross-compile for another platform. This will only work if you're version of "make" has VPATH support - which I think means GNU make. To do this:

Create a directory for the build to go in. I usually make it inside the "xqilla" directory, but that is not mandatory
Run the configure script from inside the new directory
Make the project as usual form inside the new directory

Deletions:
The build system uses autoconf, automake and libtool. It is set to build (mostly) from a single Makefile in the XQilla directory. There is a sub-directory Makefile in the "include" directory, but I only did that because I couldn't get the headers to install to the correct path otherwise.

Edited on 2005-12-14 15:58:03 by JohnSnelson

Additions:

Developer Instructions

The build system uses autoconf, automake and libtool. It is set to build (mostly) from a single Makefile in the XQilla directory. There is a sub-directory Makefile in the "include" directory, but I only did that because I couldn't get the headers to install to the correct path otherwise.

Oldest known version of this page was edited on 2005-12-14 15:53:09 by JohnSnelson []

Page view:

Linux / BSD / *nix Build Documentation

Simple Instructions

Make sure you have downloaded and build the Xerces-C library. It can be downloaded here∞.
Untar the downloaded archive
```
tar -xzvf XQilla-1.0.tar.gz
```
Change directory to the build directory -
```
cd XQilla-1.0
```

Run the configure script -

./configure --with-xerces=/path/to/xerces

Build XQilla -
```
make
```
*Optional* Install XQilla (as a super-user) -
```
make install
```

XQilla : UnixBuild

Configure Options

Useful Make Targets

Building from another directory

Building on Cygwin

Configure Options

Useful Make Targets

Building from another directory

Building on Cygwin

Linux / BSD / *nix / Cygwin Build Documentation

Linux / BSD / *nix Build Documentation

Building on Cygwin

Adding / Removing Files

Useful Make Targets

Configure Options

Building from another directory

Developer Instructions

Linux / BSD / *nix Build Documentation

Simple Instructions