> > Can you do the glob, configure the result out to a file, then INCLUDE
> that
> > file. I believe that will solve the problem. Something like
> >
> > file(GLOB SRC *.cpp)
> > configure_file(somefile.in somefile)
> > include(somefile)
> >
> > where somefile.in looks like
> >
> > # list of files a
Bill,
> Sounds like the pre-installed gcc is broken. That path should be in some
> sort of system path. Thanks for looking into this.
You bet.
The pre-installed (gcc 3.4.3) works fine. But it looks like the SUN
gcc 4.2.0 cooltools compiler has some kind of pathing issue going on
with it (or I
Hi,
I have noticed that the overwriting of CPACK_PACKAGE_VERSION have no impact
on the .deb packages file name (and have impact on sources packages).
I propose to use the CPACK_PACKAGE_VERSION_x macros only once to set
(if not set !) the CPACK_PACKAGE_VERSION and then only use the
CPACK_P
George Neill wrote:
and this is why the SUN GCC 4.2.0 (cooltools) compile fails.
-bash-3.00$ /opt/gcc/bin/gcc -lcrypto -lssl test.c
-bash-3.00$ ./a.out
ld.so.1: a.out: fatal: libcrypto.so.0.9.7: open failed: No such file
or directory
Killed
The pre-installed /usr/sfw/bin/gcc (3.4.3) compile
Brad,
This proved to be useful for me, if it is worth including ...
-bash-3.00$ cvs diff CMakeLists.txt
Index: CMakeLists.txt
===
RCS file: /cvsroot/CMake/CMake/Utilities/cmcurl/CMakeLists.txt,v
retrieving revision 1.19
diff -r1.19 C
Brad,
> I will do some more digging ...
So this is why the CMake SS12 compile works,
-bash-3.00$ /opt/SUNWspro/bin/cc -lcrypto -lssl test.c
ld: fatal: library -lcrypto: not found
ld: fatal: library -lssl: not found
ld: fatal: File processing errors. No output written to a.out
and this is why t
Brad,
More info compiling with SUN GCC 4.2 (cooltools) on sun sparc.
I think I have narrowed it to HAVE_POSIX_STRERROR_R not being defined
in Utilities/cmcurl. It seems strange since it compiles and produces
the expected results when I do it by hand.
-bash-3.00$ env | grep CC
CC=/opt/gcc/bin/gc
I have following requirement: I have big source tree (~100 projects -
libraries or binaries), and want to package them in different ways. And
encapsulate packaging knowledge in single place.
That is I want that some libraries may enter into different packages. That is
pakcageA contains libA and