In wxCode/build/bakefile/targets.bkl we have, which is similar as
COMP_WANT_UNINSTALL_WXHEADERS_TARGET.
<!-- "make install-wxheaders": -->
<if cond="COMP_WANT_INSTALL_WXHEADERS_TARGET=='1'">
<data-files-tg id="install-wxheaders">
<files>$(COMP_BASEPATH)$(DIRSEP)include$(DIRSEP)wx$(DIRSEP)*.h</files>
<if cond="TARGETING_WIN32=='1'">
<install-to>$(WX_DIR)$(DIRSEP)include$(DIRSEP)wx</install-to>
<!-- little hack over "data-files-tg" which is
truly defined only on unix -->
<set var="__copy_cmd" eval="0">
mkdir $(__dstdir)
cd $(__srcdir)
copy /Y $(__files) $(__dstdir)
</set>
<dependency-of>install</dependency-of>
<command>$(__copy_cmd)</command>
</if>
<if cond="TARGETING_WIN32=='0'">
<install-to>$(INCLUDEDIR)/wx</install-to>
</if>
</data-files-tg>
============================
BUT! If you have your includes as
wxCode/components/wxstedit/include/wx/stedit/*.h this doesn't work. I
figured that by adding "stedit" to the include path I'd avoid any
problems with name clashes.
In your user bakefile you have, optionally
<set var="COMP_INCLUDE_PATH" overwrite="0">
include$(DIRSEP)wx$(DIRSEP)/stedit
</set>
and in wxCode/build/bakefile/targets.bkl
<set var="COMP_INCLUDE_PATH" overwrite="0">
include$(DIRSEP)wx
</set>
and adjust the install and uninstall targets to use it
<!-- "make install-wxheaders": -->
<if cond="COMP_WANT_INSTALL_WXHEADERS_TARGET=='1'">
<data-files-tg id="install-wxheaders">
<files>$(COMP_BASEPATH)$(DIRSEP)$(COMP_INCLUDE_PATH)$(DIRSEP)*.h</files>
<if cond="TARGETING_WIN32=='1'">
<install-to>$(WX_DIR)$(DIRSEP)$(COMP_INCLUDE_PATH)</install-to>
<!-- little hack over "data-files-tg" which is
truly defined only on unix -->
<set var="__copy_cmd" eval="0">
mkdir $(__dstdir)
cd $(__srcdir)
copy /Y $(__files) $(__dstdir)
</set>
<dependency-of>install</dependency-of>
<command>$(__copy_cmd)</command>
</if>
<if cond="TARGETING_WIN32=='0'">
<install-to>$(INCLUDEDIR)/wx</install-to> <=== HERE!
</if>
</data-files-tg>
============================
How to make the <install-to> item work? It doesn't want the "include"
part of the path since it already has it from wxWidgets/include.
Maybe just have the user only specify "wx/stedit" and assume
everything is in "include" as in "include/wx/stedit"? Or will we run
into similar problems with some other "nonstandard" component like
mine?
Any ideas?
John Labenski
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
wxCode-users mailing list
wxCode-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wxcode-users
