On 2009-06-01 16:07-0400 Hazen Babcock wrote:

> [...]a sketch of how you'd tackle this problem [building the new pyqt
example] using the new build system would be appreciated :).

Hi Hazen:

I am going to post my reply to your question on list because I believe
others will be interested in my answer.

The important thing to remember is that the build system for the installed
examples runs independently of the build system for the PLplot core build,
but core build targets and variables are passed to the installed examples
build system using EXPORT of targets, configuration of
examples/plplot_configure.cmake_installed_examples.in (which ends up as
cmake/modules/plplot_configure.cmake in the installed examples tree), and
copying of certain unconfigured key files from the source tree such as
examples/CMakeLists.txt_installed_examples and
examples/c/CMakeLists.txt_installed_examples_c which end up
as CMakeLists.txt and c/CMakeLists.txt in the installed examples tree.

Revision 10023 is a fairly useful template for what needs to be done in
general to add a build of one particular installed example (qt_example in
this case) to this new build system.

* The qt target required to build qt_example is EXPORTed from the PLplot
core build in drivers/CMakeLists.txt.
examples/CMakeLists.txt_installed_examples already implements the import of
all such EXPORTed targets into the new build system using the
"include(export_plplot)" command.

* examples/plplot_configure.cmake_installed_examples.in is modified to
configure some additional core CMake variables to be used in the installed
examples build system to help build qt_example.

* examples/c++/CMakeLists.txt_installed_examples_cxx (which is copied to
c/CMakeLists.txt in the installed examples tree ) is modified to do the
actual build of qt_example using the targets and CMake variables that are
available from the core build as well as anything independent that it needs
to do itself.  A complication for this qt_example case was I needed access
to the qt4_wrap_cpp macro.  Thus, as documented in
examples/c++/CMakeLists.txt_installed_examples_cxx, I had to find Qt4 all
over again to get access to that macro (with some care to make sure it was
the same as the Qt4 used in the core version), but normally if you don't
need such cmake system macros, you would just pass variables like
QT_LIBRARIES directly from the core build without having to determine them
all over again with a system Find module.

Thanks for your interest in using the new build system for the installed
examples to build your new pyqt example.  I hope the above general
explanation will help you toward that goal.  I will take a look at that
example this afternoon to see if there is anything more I can say to you
(off list) to help you with that specific build.

Alan
__________________________
Alan W. Irwin

Astronomical research affiliation with Department of Physics and Astronomy,
University of Victoria (astrowww.phys.uvic.ca).

Programming affiliations with the FreeEOS equation-of-state implementation
for stellar interiors (freeeos.sf.net); PLplot scientific plotting software
package (plplot.org); the libLASi project (unifont.org/lasi); the Loads of
Linux Links project (loll.sf.net); and the Linux Brochure Project
(lbproject.sf.net).
__________________________

Linux-powered Science
__________________________

------------------------------------------------------------------------------
OpenSolaris 2009.06 is a cutting edge operating system for enterprises 
looking to deploy the next generation of Solaris that includes the latest 
innovations from Sun and the OpenSource community. Download a copy and 
enjoy capabilities such as Networking, Storage and Virtualization. 
Go to: http://p.sf.net/sfu/opensolaris-get
_______________________________________________
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel

Reply via email to