Get XQilla at SourceForge.net. Fast, secure and Free Open Source software downloads

XQilla : UnixBuild

HomePage :: PageIndex :: RecentChanges :: RecentlyCommented :: Login/Register
Most recent edit on 2012-01-30 09:58:09 by JohnSnelson [Reverted to version from 2011-11-16 00:22:00]

Deletions:
friv games



Edited on 2012-01-24 11:04:48 by DanaGheorghe [minor]

Additions:
friv games



Edited on 2011-11-16 00:22:00 by JohnSnelson [Reverted to version from 2010-03-29 09:38:20]

Deletions:
fussballwetten



Edited on 2011-09-21 03:20:17 by Erikvarden06 [fussballwetten]

Additions:
fussballwetten



Edited on 2010-03-29 09:38:20 by JohnSnelson [Reverted to version from 2009-12-14 14:19:17]

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:
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:


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 custom term papers to the generated Makefile. Open the Makefile and find the line that looks like:
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 writers resumes of a Makefile line that will link you objects to XQilla and Xerces under Cygwin:




Edited on 2010-03-23 15:35:14 by AbigailJohnson [minor]

Additions:
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 writers resumes of a Makefile line that will link you objects to XQilla and Xerces under Cygwin:

Deletions:
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 writer/s resumes of a Makefile line that will link you objects to XQilla and Xerces under Cygwin:



Edited on 2010-03-23 15:33:42 by AbigailJohnson [minor]

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 custom term papers to the generated Makefile. Open the Makefile and find the line that looks like:
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 writer/s resumes of a Makefile line that will link you objects to XQilla and Xerces under Cygwin:


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:
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:




Edited on 2009-12-14 14:19:17 by JohnSnelson [Reverted to version from 2009-10-14 11:47:08]

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.

Deletions:
~&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.



Edited 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
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:
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.
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
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:
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 2007-01-25 03:38:29 by JohnSnelson

Additions:

Linux / BSD / *nix / Cygwin Build Documentation



Deletions:

Linux / BSD / *nix Build Documentation





Oldest known version of this page was edited on 2007-01-23 13:09:19 by TmsExnebula []
Page view:

Linux / BSD / *nix Build Documentation


Simple Instructions


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.

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.


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

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:

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
Powered by Wikka Wakka Wiki 1.1.6.0
Page was generated in 0.1320 seconds