I made some RPM building specfiles for
stlsoft and recls, maybe they can get
included in future versions  of them ?

(although they do need to have their
version numbers kept up-to-date, if so,
and I am *not* volunteering to do that...)

http://www.algonet.se/~afb/d/stlsoft.spec
http://www.algonet.se/~afb/d/stlsoft-config.in

Builds:
1.3M    stlsoft-1.8.3-0.4beta.src.rpm
612K    stlsoft-1.8.3-0.4beta.noarch.rpm

http://www.algonet.se/~afb/d/recls.spec
http://www.algonet.se/~afb/d/recls-config.in

Builds:
1.8M    recls-1.6.1-1.src.rpm
608K    recls-1.6.1-1.i386.rpm

    ****

I was not able to build either of them
on Red Hat Linux 7.3, using GCC 2.96 ?

I'm not sure if that's really a problem,
since most everyone is using GCC 3 now.


And when I tried to build beta 5 with GCC 3,
I got the following g++ error from RPMs make:

> In file included from ../../unixstl/unittest.0.cpp:60:
> /usr/src/redhat/BUILD/stlsoft-1.8.3/unixstl_exceptions.h: In constructor `
>    stlsoft::unixstl_project::unix_exception::unix_exception(int)':
> /usr/src/redhat/BUILD/stlsoft-1.8.3/unixstl_exceptions.h:115: error: class `
>    stlsoft::unixstl_project::unix_exception' does not have any field named `
>    m_reason'

    ****

But using beta 4 and GCC 3.3.2 worked fine:
(testing, using the bundled C/C++ sample code)

> gcc -Wall /usr/share/doc/recls-1.6.1/C.c \
>     `recls-config --cflags` `recls-config --libs`

> g++ -Wall /usr/share/doc/recls-1.6.1/Cpp.cpp \
>     `recls-config --cxxflags` `recls-config --libs`

"stlsoft-config" and "recls-config" are small
shell scrips that return the needed settings.

In this case, they outputted:
> -I/usr/include/stlsoft -I/usr/include/stlsoft/inprogress
> -I/usr/include/recls -L/usr/lib -lrecls -lstdc++

Such -config scripts are pretty common on Linux.

--anders

Thanks Anders

I'll digest this stuff soon(-ish). Hopefully when I release 1.8.3 I can do SRPMS, and from then on for all future versions.

Cheers

Matthew

"Anders F Björklund" <afb@algonet.se> wrote in message news:d2scdn$6tq$2@digitaldaemon.com...
>I made some RPM building specfiles for
> stlsoft and recls, maybe they can get
> included in future versions  of them ?
>
> (although they do need to have their
> version numbers kept up-to-date, if so,
> and I am *not* volunteering to do that...)
>
> http://www.algonet.se/~afb/d/stlsoft.spec http://www.algonet.se/~afb/d/stlsoft-config.in
>
> Builds:
> 1.3M    stlsoft-1.8.3-0.4beta.src.rpm
> 612K    stlsoft-1.8.3-0.4beta.noarch.rpm
>
> http://www.algonet.se/~afb/d/recls.spec http://www.algonet.se/~afb/d/recls-config.in
>
> Builds:
> 1.8M    recls-1.6.1-1.src.rpm
> 608K    recls-1.6.1-1.i386.rpm
>
>     ****
>
> I was not able to build either of them
> on Red Hat Linux 7.3, using GCC 2.96 ?
>
> I'm not sure if that's really a problem,
> since most everyone is using GCC 3 now.
>
>
> And when I tried to build beta 5 with GCC 3,
> I got the following g++ error from RPMs make:
>
>> In file included from ../../unixstl/unittest.0.cpp:60:
>> /usr/src/redhat/BUILD/stlsoft-1.8.3/unixstl_exceptions.h: In constructor `
>>    stlsoft::unixstl_project::unix_exception::unix_exception(int)':
>> /usr/src/redhat/BUILD/stlsoft-1.8.3/unixstl_exceptions.h:115: error: class `
>>    stlsoft::unixstl_project::unix_exception' does not have any field named `
>>    m_reason'
>
>     ****
>
> But using beta 4 and GCC 3.3.2 worked fine:
> (testing, using the bundled C/C++ sample code)
>
>> gcc -Wall /usr/share/doc/recls-1.6.1/C.c \
>>     `recls-config --cflags` `recls-config --libs`
>
>> g++ -Wall /usr/share/doc/recls-1.6.1/Cpp.cpp \
>>     `recls-config --cxxflags` `recls-config --libs`
>
> "stlsoft-config" and "recls-config" are small
> shell scrips that return the needed settings.
>
> In this case, they outputted:
>> -I/usr/include/stlsoft -I/usr/include/stlsoft/inprogress -I/usr/include/recls -L/usr/lib -lrecls -lstdc++
>
> Such -config scripts are pretty common on Linux.
>
> --anders

Matthew wrote:

> I'll digest this stuff soon(-ish).

No problem, mostly did them for myself anyway...

> Hopefully when I release 1.8.3 I can do SRPMS,
> and from then on for all future versions.

Actually you don't have to provide any SRPMS, if you
just include the ".spec" and the "config.in" files
(and keep the version numbers inside them updated) -
then it's trivial to download the ZIPs and make one ?


Here are the file contents of such a Source RPM:

# rpm -qplv stlsoft-1.8.3-0.6beta.src.rpm
1162523 Apr  5 10:00 stlsoft-1.8.3-beta6.zip
 212160 Mar  2 00:25 stlsoft-1.8.3-unittests.zip
    651 Apr  4 15:31 stlsoft-config.in
   3373 Apr  5 10:07 stlsoft.spec

As you can, see most of the download is just the zips ?
(which are identical to the ones on the download page,
so providing both of them is mostly a waste of space...)


Currently the stlsoft.spec says:
> Name: stlsoft
> Version: 1.8.3
> %define subvers -beta6
> Release: 0.6beta

When you are done, it would be:
> Name: stlsoft
> Version: 1.8.3
> %define subvers %{nil}
> Release: 1

And that's pretty much the only change you need to do.
(I think you can figure out how to do a "Beta 7" :-) )

--anders

PS. Here's a tool you might find handy:
    http://rpmwin32.sourceforge.net/