On 2007-01-07 14:11:44 -0800 Nicola Pero
<[EMAIL PROTECTED]> wrote:
Someone on irc was wondering about ctools and c++ files,
clibrary.make seemed to work ok though.
it doesn't seem to currently include $(CC_OBJC_FILES).
attached is a patch for that..
Thanks ... good stuff ... I cleaned it up so it's a bit more general,
and committed. :-)
additionally i was wondering why it doesn't use g++ to compile the
files?
also when linking executables with c++ objs shouldn't it use g++ to
link?
I can see how you could just add -lstdc++ to the ADDITIONAL_TOOL_LIBS
but i also suppose a user could have multiple libstdc++'s and using
g++ should make sure that the correct libstdc++ is linked in or
something
Interesting ... btw what happens when you compile ObjC++ ? ;-)
Thats a good question. :D
actually i'm not sure if what i said above is actually true, but it'd
make sense as to why g++ automatically links to it
anyhow it was more an observation, i have no idea what (if anything)
to do about it :D
Comments from any actual C++ / ObjC++ user would be very welcome. :-)
Indeed....
Don't mean to hijack this thread. but heres another thing
documentation.make installs TEXI_FILES files into
Library/Documentation/info
heres a patch to set this up in the INFOPATH env var from GNUstep.sh
i suppose there should be a configure switch to allow someone to set
the info path dir to /usr/share/info (or whereever)
when configuring gnustep like there is to force libs into /usr/lib but
this isn't taken care of by the patch.
also i noticed the guile was using /Libraries instead of
Library/Libraries changed that too.. (untested)
<infopath.diff>
Index: GNUstep.sh.in
===================================================================
--- GNUstep.sh.in (revision 24324)
+++ GNUstep.sh.in (working copy)
@@ -355,7 +355,33 @@
export GUILE_LOAD_PATH
unset guile_paths
+old_IFS="$IFS"
+IFS=:
+info_paths=
+for dir in $GNUSTEP_PATHLIST; do
+ if [ -z "$info_paths" ]; then
+ info_paths="$dir/Library/Documentation/info"
+ else
+ info_paths="$info_paths:$dir/Library/Documentation/info"
+ fi
+
+done
+IFS="$old_IFS"
+unset old_IFS
+unset dir
+
+if [ -z "$INFOPATH" ]; then
+ INFOPATH="$info_paths"
+else
+ if ( echo ${INFOPATH}| grep -v "${info_paths}" >/dev/null ); then
+ INFOPATH="$info_paths:$INFOPATH"
+ fi
+fi
+
+export INFOPATH
+unset info_paths
+
#
# Perform any user initialization
#
Index: GNUstep.csh.in
===================================================================
--- GNUstep.csh.in (revision 24324)
+++ GNUstep.csh.in (working copy)
@@ -207,7 +207,7 @@
unset gnustep_class_path
-set
gnustep_guile_path="${GNUSTEP_USER_ROOT}/Libraries/Guile:${GNUSTEP_LOCAL_ROOT}/Libraries/Guile:${GNUSTEP_NETWORK_ROOT}/Libraries/Guile:${GNUSTEP_SYSTEM_ROOT}/Libraries/Guile"
+set
gnustep_guile_path="${GNUSTEP_USER_ROOT}/Library/Libraries/Guile:${GNUSTEP_LOCAL_ROOT}/Library/Libraries/Guile:${GNUSTEP_NETWORK_ROOT}/Library/Libraries/Guile:${GNUSTEP_SYSTEM_ROOT}/Library/Libraries/Guile"
if ( $?GUILE_LOAD_PATH == 0 ) then
setenv GUILE_LOAD_PATH "${gnustep_guile_path}"
@@ -217,6 +217,16 @@
unset gnustep_guile_path
+set
gnustep_info_path="${GNUSTEP_USER_ROOT}/Library/Documentation/info:${GNUSTEP_LOCAL_ROOT}/Library/Documentation/info:${GNUSTEP_NETWORK_ROOT}/Library/Documentation/info:${GNUSTEP_SYSTEM_ROOT}/Library/Documentation/info"
+
+if ( $?INFOPATH == 0 ) then
+ setenv INFOPATH "${gnustep_info_path}"
+else if ( { (echo "${INFOPATH}" | fgrep -v "${gnustep_info_path}" >/dev/null)
} ) then
+ setenv INFOPATH "${gnustep_info_path}:${INFOPATH}"
+endif
+
+unset gnustep_info_path
+
#
# Perform any user initialization
#
Index: GNUstep-reset.sh
===================================================================
--- GNUstep-reset.sh (revision 24324)
+++ GNUstep-reset.sh (working copy)
@@ -87,6 +87,7 @@
reset_path DYLD_LIBRARY_PATH /Library/Libraries
reset_path DYLD_FRAMEWORK_PATH /Library/Frameworks
reset_path PATH /Tools
+reset_path INFOPATH Library/Documentation/info
# Make sure we destroy the reset_path function after using it - we don't
# want to pollute the environment with it.
_______________________________________________
Gnustep-dev mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/gnustep-dev
