-and quite possibly
-
-GNU make
-GNU cc
-
-and if you have all this then you probably know enough to
-go ahead yourself :-)
-
-** Something about Makefiles
-------------------------------
-
-On general principle it should only contain ONE line, which is as follows:
-
- include ../../setup/general/makeapp
-
-this will include all the necessary definitions for creating the applications
-
-the only case where you might want to add another line is the following:
-this version of configure also supports creation of source archives of the
-application for easy distribution and updates to newer version of wxWindows.
- For this purpose all files in the application-directory will be put into
-a gziped tar-file in the full notation user/<your application>/*
-if you want to include some other files that you want "more visible", like
-a README.<yourApp> or a shell script for easy
-compilation/installation/distribution, then you have to add a variable
-
- DISTRIBUTE_ADDITIONAL=<your files>
-
-to the Makefile.
-So it would look like this:
-
- DISTRIBUTE_ADDITIONAL=README.TheApp
- include ../../setup/general/makeapp
-
-As we have already talked about distribution the command to create a
-distribution is:
-
- make distrib
-
-NOTE: If you are in the base directory of wxWindows it will create
-distribution packages for wxWindows as well as for all packages in the
-user directory.
- So if you want to create only packages for the files in user,
-then go to the directory other and type:
-
- make distrib
-
-or if you only want one application to be created then
-enter the specific directory and type there:
-make distrib
-
-All the distribution files will be put in the directory
-distrib at the base of the wxWindows-tree (where also configure
-and template.mak can be found).
-
-** Something about Makefile.in
---------------------------------
-
-As you have already seen with Makefile, configure makes a lot of use
-if the include statement in make to keep the Makefiles as simple as
-possible.
-
-So basically there are only variables to define and then a include command.
-Exception to this rule is if you have special rules for some stuff...
-These rules should go AFTER the include statement!!!
-
-so the general header looks like this:
-
- # wxWindows base directory
- WXBASEDIR=@WXBASEDIR@
- # set the OS type for compilation
- OS=@OS@
- # compile a library only
- RULE=bin
-
-and the general footer will look like this:
-
- # include the definitions now
- include ../../../template.mak
-
-the key variable is RULE, which defines what make should create
-in this directory.
-
-here are some examples:
-
- RULE description
- ===========================================================================
- bin creates a local binary (for a global binary prefix bin with g)
- additional variables needed:
- BIN_TARGET this gives the name of your application
- BIN_OBJ this gives the object files needed to
- link the application
- optional variables are:
- BIN_SRC this gives the list of c/c++ files for
- which dependencies will be checked.
- (This can be achieved with: make depend)
- BIN_LINK this gives commands for additional
- libraries needed to link the application
- ---------------------------------------------------------------------------
- bin2 creates two local binaries (for global binaries prefix bin2 with g)
- in addition to the variables specified above you MUST also
- provide the same variables with BIN2_ instead of BIN_
- ---------------------------------------------------------------------------
- lib creates a local library (for a global binary prefix bin with g)
- additional variables needed:
- LIB_TARGET this gives the name of your library
- LIB_OBJ this gives the object files needed for
- the library to be build.
- optional variables are:
- LIB_SRC this gives the list of c/c++ files for
- which dependencies will be checked.
- libbin and libgbin are also possible and will need in addition
- the variables from bin
- ---------------------------------------------------------------------------
- gslib is similar to lib, but it creates a shared library if the system
- supports it.
- additional variables needed:
- LIB_MAJOR major number of the shared library
- LIB_MINOR minor number of the shared library
- ---------------------------------------------------------------------------
- other additional variables:
-
- ADD_COMPILE define additional includes/defines that
- are needed to compile the object files
- (if you need to reference some directory
- utils - like wxGrid -, then please
- reference them with the variables defined
- in template.mak - e.g.: $(SRCDIR),$(UTILS),
- $(SAMPLES),$(OTHERS))
-
- NEEDED_DEFINES lists all the defines that HAVE to be set in
- /include/wx/setup.h to compile correctly.
-
- SRC_DIR lists all directories that are needed to
- compile. (i.e: lists all the directories,
- where there are source-files.) But it is
- also needed to clean an object and for
- machines, for which make does not support
- VPATH
-
-currently there are the following compiling rules provided:
-object files are created for the following file extensions:
-.c .cc .cpp
-
-Please have a closer look at the Makefiles in this distribution.
-
-* Platforms configure is working with
----------------------------------------
-
-Please report build succes on any machine. Especially non-
-Linux operating systems (which I don't have).
-
-Original author of the autoconf system for wxxt-1.66 and for this INSTALL
-file:
-
- Martin Sperl sperl@dsn.ast.univie.ac.at
-
-Ported to wxGTK 0.1:
-
- Wolfram Gloger wmglo@dent.med.uni-muenchen.de
-
-Thanks alot to both of them.
projects / wxWidgets.git / blobdiff