corelinux-develop

[Corelinux-develop] Major update!

[Christophe Prud'h. <pru...@MI...>]

Hi all,

I just upgraded my cvs and there a few important changes:

- added doxygen support
  install CVS version of doxygen 
  everything is at 

   http://www.stack.nl/~dimitri/doxygen/index.html

  the patches I sent for pdf might not be in the CVS yet
  so the pdf might look ugly

  don't worry I didn't put the reference manual into CVS
  you can't generate it using doxygen by doing:
  
  cd doc 
  doxygen corelinux.cfg
 
  corelinux.css is the style sheet for the html files
  corelinux.html is the footer for the html files

- now use -lcl++ to link against corelinux
  all the Makefile.am have been change automagically
  (see src/testdrivers/update_makefile.pl)

- now use the libtool versioning system for shared libraries!

- update package creation
  4 packages are created

  * libcorelinux the same as always
  * libcorelinux-dev added manpages !
  * libcorelinux-doc html + ps + pdf reference manual
  * libcorelinux-examples the examples for corelinux
    o they are ALL in /usr/share/doc/libcorelinux-examples/examples/
      there is a Makefile which automagically generated during the 
      package creation (see debian/genmake.pl)
    o a README.examples explains how to compile the example but 
      don't fear it is pretty straightforward

- the package for 0.4.26 (with -1 package version) have been uploaded
  to corelinux.sourceforge.net/packages
  Please give them a try and tell, especially undeer redhat, if 
  everything is ok
  On debian side I am an happy corelinux user and package maintainer
  I learnt a few interesting things tonight :)


As you can see I had fun this night!
time to go to bed, good night
C.

-- 
Christophe Prud'homme                |
MIT, 77, Mass Ave, Rm 3-243          | He that breaks a thing to find out
Cambridge MA 02139                   | what it is has left the path of wisdom.
Tel (Office) : (00 1) (617) 253 0229 | -- J.R.R. Tolkien
Fax (Office) : (00 1) (617) 258 8559 |
http://augustine.mit.edu/~prudhomm   |
                          Following the hacker spirit

[Corelinux-develop] manual pages

[Christophe Prud'h. <pru...@MI...>]

As I said the manual pages are in libcorelinux-dev
doxygen generates the name of the manual pages using
the namespace and the object or the interface

to viewing StorageException manual pages
you type

man corelinux__StorageException

C.

Re: [Corelinux-develop] Major update!

[Frank V. C. <fr...@co...>]

Busy person eh?

Some questions:

1. Am I correct you pulled doxygens cvs tree and built with your
patches?
2. In the corelinux.cfg there is a version defined. This, I take it, is
manually updated for each release?

Maybe more to come


Christophe Prud'homme wrote:
> 
> Hi all,
> 
> I just upgraded my cvs and there a few important changes:
> 
> - added doxygen support
>   install CVS version of doxygen
>   everything is at
> 
>    http://www.stack.nl/~dimitri/doxygen/index.html
> 
>   the patches I sent for pdf might not be in the CVS yet
>   so the pdf might look ugly
> 
>   don't worry I didn't put the reference manual into CVS
>   you can't generate it using doxygen by doing:
> 
>   cd doc
>   doxygen corelinux.cfg
> 
>   corelinux.css is the style sheet for the html files
>   corelinux.html is the footer for the html files
> 
> - now use -lcl++ to link against corelinux
>   all the Makefile.am have been change automagically
>   (see src/testdrivers/update_makefile.pl)
> 
> - now use the libtool versioning system for shared libraries!
> 
> - update package creation
>   4 packages are created
> 
>   * libcorelinux the same as always
>   * libcorelinux-dev added manpages !
>   * libcorelinux-doc html + ps + pdf reference manual
>   * libcorelinux-examples the examples for corelinux
>     o they are ALL in /usr/share/doc/libcorelinux-examples/examples/
>       there is a Makefile which automagically generated during the
>       package creation (see debian/genmake.pl)
>     o a README.examples explains how to compile the example but
>       don't fear it is pretty straightforward
> 
> - the package for 0.4.26 (with -1 package version) have been uploaded
>   to corelinux.sourceforge.net/packages
>   Please give them a try and tell, especially undeer redhat, if
>   everything is ok
>   On debian side I am an happy corelinux user and package maintainer
>   I learnt a few interesting things tonight :)
> 
> As you can see I had fun this night!
> time to go to bed, good night
> C.
> 
> --
> Christophe Prud'homme                |
> MIT, 77, Mass Ave, Rm 3-243          | He that breaks a thing to find out
> Cambridge MA 02139                   | what it is has left the path of wisdom.
> Tel (Office) : (00 1) (617) 253 0229 | -- J.R.R. Tolkien
> Fax (Office) : (00 1) (617) 258 8559 |
> http://augustine.mit.edu/~prudhomm   |
>                           Following the hacker spirit
> 
> _______________________________________________
> Corelinux-develop mailing list
> Cor...@li...
> http://lists.sourceforge.net/mailman/listinfo/corelinux-develop

-- 
Frank V. Castellucci
http://corelinux.sourceforge.net
OOA/OOD/C++ Standards and Guidelines for Linux
http://PythPat.sourceforge.net
Pythons Pattern Package

Re: [Corelinux-develop] Major update!

[Christophe Prud'h. <pru...@MI...>]

    Frank> Busy person eh?  Some questions:
Well yes
I couldn't stop

    Frank> 1. Am I correct you pulled doxygens cvs tree and built with your
    Frank> patches?
yes but my patches allowed doxygen to generate the doc for pdflatex and 
the associated makefile 
did you install doxygen?

    Frank> 2. In the corelinux.cfg there is a version defined. This, I take it, is
    Frank> manually updated for each release?
yes but using configure we can update this automatically
I will do that !

    Frank> First problems found:
it has to happen
I have little control over the redhat packaging

    Frank> Using RPM to install the libcorelinux-0.4.26-1.i386.rpm:

    Frank> 1. The entry is put in the database entry "Converted/libs" branch,
    Frank> should go into "System Environment/Libraries"
Ok I 'll what I can do

    Frank> 2. When uninstalling RPM complains that it can't delete "/"
That's bad very bad behaviour

    Frank> If you want I can start tracking these for you in the BugTracking
yes


yesterday I recompiled kde2 on my machine
and I am an happy man :)
very fast, beautiful feature full, a bliss but still beta

C.

Re: [Corelinux-develop] Major update!

[Frank V. C. <fr...@co...>]

Christophe Prud'homme wrote:

>     Frank> 1. Am I correct you pulled doxygens cvs tree and built with your
>     Frank> patches?
> yes but my patches allowed doxygen to generate the doc for pdflatex and
> the associated makefile
> did you install doxygen?

I dl'ed the rpm but I stopped from installing because I remembered your patch note. I
guess I'll get the CVS and ask for your patch.

>     Frank> 2. In the corelinux.cfg there is a version defined. This, I take it, is
>     Frank> manually updated for each release?
> yes but using configure we can update this automatically
> I will do that !

Have you had enough sleep yet?

>     Frank> First problems found:
> it has to happen
> I have little control over the redhat packaging

I imagine, I guess it's about time for me to learn RPM nuances as I am on a RH
distribution anyway. Let me see what I can come up with.

>     Frank> Using RPM to install the libcorelinux-0.4.26-1.i386.rpm:
>
>     Frank> 1. The entry is put in the database entry "Converted/libs" branch,
>     Frank> should go into "System Environment/Libraries"
> Ok I 'll what I can do

I am at work on a contract today, I will get into RPM manifests and whatever later on
tonight or during the weekend.

>     Frank> 2. When uninstalling RPM complains that it can't delete "/"
> That's bad very bad behaviour

I'll say :)

>     Frank> If you want I can start tracking these for you in the BugTracking
> yes
>

Will do, I'll test the develop package later tonight. I'll add the others in the
meantime.

Frank

Re: [Corelinux-develop] Major update!

[Christophe Prud'h. <pru...@MI...>]

>>>>> "Frank" == Frank V Castellucci <fr...@co...> writes:

    Frank> Christophe Prud'homme wrote:

    Frank> 1. Am I correct you pulled doxygens cvs tree and built with your
    Frank> patches?
    >> yes but my patches allowed doxygen to generate the doc for pdflatex and the associated
    >> makefile did you install doxygen?
    Frank> I dl'ed the rpm but I stopped from installing because I remembered your patch note. I
    Frank> guess I'll get the CVS and ask for your patch.
Oh it will work perfectly without my patches
my patches are only for pdf generation and in a cosmetic way !

  
    Frank> 2. In the corelinux.cfg there is a version defined. This, I take it, is
    Frank> manually updated for each release?
    >> yes but using configure we can update this automatically I will do that !

    Frank> Have you had enough sleep yet?
actuallly I arrived at 1oclock so I guess I am all right :)
the thing is that the lab is very noisy during the day and
I need to be in a quiet place to be able to work correctly

    Frank> I imagine, I guess it's about time for me to learn RPM nuances as I am on a RH
    Frank> distribution anyway. Let me see what I can come up with.
there are several tools to create rpm packages
they will create a .spec file

    Frank> Will do, I'll test the develop package later tonight. I'll add the others in the
    Frank> meantime.
Ok

I have already made a few changes (like the auto versioning for doxygen)

did you try to compile the examples with the system I set up?

C.

Re: [Corelinux-develop] Major update!

[Frank V. C. <fr...@co...>]

Christophe Prud'homme wrote:

> >>>>> "Frank" == Frank V Castellucci <fr...@co...> writes:
>
>     Frank> Christophe Prud'homme wrote:
>
>     Frank> 1. Am I correct you pulled doxygens cvs tree and built with your
>     Frank> patches?
>     >> yes but my patches allowed doxygen to generate the doc for pdflatex and the associated
>     >> makefile did you install doxygen?
>     Frank> I dl'ed the rpm but I stopped from installing because I remembered your patch note. I
>     Frank> guess I'll get the CVS and ask for your patch.
> Oh it will work perfectly without my patches
> my patches are only for pdf generation and in a cosmetic way !

Ok, will install when I get back home.

>     Frank> 2. In the corelinux.cfg there is a version defined. This, I take it, is
>     Frank> manually updated for each release?
>     >> yes but using configure we can update this automatically I will do that !

Check

>     Frank> Have you had enough sleep yet?
> actuallly I arrived at 1oclock so I guess I am all right :)
> the thing is that the lab is very noisy during the day and
> I need to be in a quiet place to be able to work correctly

After having two children, I can work on the NY Subway

>     Frank> I imagine, I guess it's about time for me to learn RPM nuances as I am on a RH
>     Frank> distribution anyway. Let me see what I can come up with.
> there are several tools to create rpm packages
> they will create a .spec file

I remember seeing some, I will do a full search at some point tonight.

>     Frank> Will do, I'll test the develop package later tonight. I'll add the others in the
>     Frank> meantime.
> Ok
>
> I have already made a few changes (like the auto versioning for doxygen)
>
> did you try to compile the examples with the system I set up?

Not yet, I had to leave the comfort of my own home to, you won't believe this, go to work! Which, by
the way, I am convinced is to just support my wine intake.

Frank

[Corelinux-develop] including corelinux in a project with autoconf

[Christophe Prud'h. <pru...@MI...>]

Hi,

lots of Linux projects use autoconf out there
so being able to check corelinux existence using autoconf 
would be nice. Unfortunately autoconf doesn't support well
C++ in the sense that to check libs it uses a m4 macro
AC_CHECK_LIB this way

AC_CHECK_LIB(cl++, ACCheckCoreLinux,[
CXXFLAGS="${CXXFLAGS} -I/usr/include/corelinux"
LDFLAGS="${LDFLAGS} "
LIBS="${LIBS} -lcl++"
],[
 echo "You need to install corelinux. see http://corelinux.sourceforge.net"
 exit;
],)

where cl++ is corelinux lib and ACCheckCoreLinux some symbol to check in cl++
but the c++ mangler won't create the symbol ACCheckCoreLinux(more likely
ACCheckCoreLinux__Fv) and AC_CHECK_LIB will create a C program

char ACCheckCoreLinux();
 
int main() {
ACCheckCoreLinux()
; return 0; }        

and the above test will fail :(
that is bad !

So people have to create their own checking m4 macros for corelinux
or bypass the checking of corelinux existence.

We can help them by proving this symbol in corelinux 
by defining this dummy function using extern "C"

extern "C" {
  int
  ACCheckCoreLinux()
  {
    return 1;
  }


and put it in libcl++ 
and yes it should be documented in the Developper manual 
so that any autoconf user will be very happy. (see the macro above)


well I have already done it in my cvs copy.

comments?

it seems I like long mails recently :)
C. 

-- 
Christophe Prud'homme                |
MIT, 77, Mass Ave, Rm 3-243          | He that breaks a thing to find out
Cambridge MA 02139                   | what it is has left the path of wisdom.
Tel (Office) : (00 1) (617) 253 0229 | -- J.R.R. Tolkien
Fax (Office) : (00 1) (617) 258 8559 |
http://augustine.mit.edu/~prudhomm   |
                          Following the hacker spirit

Re: [Corelinux-develop] including corelinux in a project with autoconf

[Gabriel D. R. <Gab...@cm...>]

"Christophe Prud'homme" <pru...@MI...> writes:

| Hi,
| 
| lots of Linux projects use autoconf out there
| so being able to check corelinux existence using autoconf 
| would be nice. Unfortunately autoconf doesn't support well
| C++ in the sense that to check libs it uses a m4 macro
| AC_CHECK_LIB this way

We've been using succesfully autoconf in the listdc++-v3 project.
Perhaps you might want to talk to pm...@so... who has
been spending times on getting autoconf work for us.

-- Gaby

Re: [Corelinux-develop] including corelinux in a project with autoconf

[Christophe Prud'h. <pru...@MI...>]

Bonjour :)

in fact in the mail I gave the solution (the easy way for any
corelinux user) it is documented, implemented and tested in my own code
using corelinux with autoconf, in the autoconf way,  is NO problem now.

It was just a dramatic introduction, but the end is full of hope
they got married and will have lots of children :)

BTW I've been following your work on G++ libstdc++ and above all
expression template(I am a blitz user) since a long time now(great work)
I think you gave a talk to the C++ day for scientific computing
in Paris organized by my former thesis advisor O Pironneau.

regards
C.

-- 
  Christophe Prud'homme                 |  Its name is Public Opinion.
  MIT, 77, Mass Ave, Rm 3-243           |  It is held in reverence.
  Cambridge MA 02139                    |  It settles everything.
  Tel (Office) : (00 1) (617) 253 0229  |  Some think it is the voice of God.
  Fax (Office) : (00 1) (617) 258 8559  |  -- Mark Twain
  http://augustine.mit.edu/~prudhomm    |
                          Following the hacker spirit

Re: [Corelinux-develop] including corelinux in a project with autoconf

[Christophe Prud'h. <pru...@MI...>]

I forgot to add:

corelinux uses autoconf/automake/libtool tool chain since a few months 
now when I managed to convince? Frank about the power of these tooks :)
The issue was about providing a way to corelinux users using autoconf
to check corelinux existence(-lcl++) in the autoconf way (AC_CHECK_LIB). 

C.

-- 
  Christophe Prud'homme                  |
  MIT, 77, Mass Ave, Rm 3-243            |   As flies to wanton boys are we
  Cambridge MA 02139                     |   to the gods; they kill us for
  Tel (Office) : (00 1) (617) 253 0229   |   their sport.
  Fax (Office) : (00 1) (617) 258 8559   |   -- Shakespeare, "King Lear"
  http://augustine.mit.edu/~prudhomm     |
                          Following the hacker spirit

Re: [Corelinux-develop] including corelinux in a project with autoconf

[Gabriel D. R. <Gab...@cm...>]

"Christophe Prud'homme" <pru...@MI...> writes:

| I forgot to add:
| 
| corelinux uses autoconf/automake/libtool tool chain since a few months 

Thanks you for the reminder.

Actually, I have to confess that due to lack of time I didn't have,
unfortunately, the opportunity to take a closer look at your work.
However, I'm going on vacation next week so I'll print the docs and,
hopefully, read them carefully :-)

Thanks.

-- Gaby

Re: [Corelinux-develop] Major update!

[Frank V. C. <fr...@co...>]

First problems found:

Using RPM to install the libcorelinux-0.4.26-1.i386.rpm:

1. The entry is put in the database entry "Converted/libs" branch,
should go into "System Environment/Libraries"
2. When uninstalling RPM complains that it can't delete "/"

If you want I can start tracking these for you in the BugTracking

Christophe Prud'homme wrote:
> 
> Hi all,
> 
> I just upgraded my cvs and there a few important changes:
> 
> - added doxygen support
>   install CVS version of doxygen
>   everything is at
> 
>    http://www.stack.nl/~dimitri/doxygen/index.html
> 
>   the patches I sent for pdf might not be in the CVS yet
>   so the pdf might look ugly
> 
>   don't worry I didn't put the reference manual into CVS
>   you can't generate it using doxygen by doing:
> 
>   cd doc
>   doxygen corelinux.cfg
> 
>   corelinux.css is the style sheet for the html files
>   corelinux.html is the footer for the html files
> 
> - now use -lcl++ to link against corelinux
>   all the Makefile.am have been change automagically
>   (see src/testdrivers/update_makefile.pl)
> 
> - now use the libtool versioning system for shared libraries!
> 
> - update package creation
>   4 packages are created
> 
>   * libcorelinux the same as always
>   * libcorelinux-dev added manpages !
>   * libcorelinux-doc html + ps + pdf reference manual
>   * libcorelinux-examples the examples for corelinux
>     o they are ALL in /usr/share/doc/libcorelinux-examples/examples/
>       there is a Makefile which automagically generated during the
>       package creation (see debian/genmake.pl)
>     o a README.examples explains how to compile the example but
>       don't fear it is pretty straightforward
> 
> - the package for 0.4.26 (with -1 package version) have been uploaded
>   to corelinux.sourceforge.net/packages
>   Please give them a try and tell, especially undeer redhat, if
>   everything is ok
>   On debian side I am an happy corelinux user and package maintainer
>   I learnt a few interesting things tonight :)
> 
> As you can see I had fun this night!
> time to go to bed, good night
> C.
> 
> --
> Christophe Prud'homme                |
> MIT, 77, Mass Ave, Rm 3-243          | He that breaks a thing to find out
> Cambridge MA 02139                   | what it is has left the path of wisdom.
> Tel (Office) : (00 1) (617) 253 0229 | -- J.R.R. Tolkien
> Fax (Office) : (00 1) (617) 258 8559 |
> http://augustine.mit.edu/~prudhomm   |
>                           Following the hacker spirit
> 
> _______________________________________________
> Corelinux-develop mailing list
> Cor...@li...
> http://lists.sourceforge.net/mailman/listinfo/corelinux-develop

-- 
Frank V. Castellucci
http://corelinux.sourceforge.net
OOA/OOD/C++ Standards and Guidelines for Linux
http://PythPat.sourceforge.net
Pythons Pattern Package

Re: [Corelinux-develop] including corelinux in a project with autoconf

[Frank V. C. <fr...@co...>]

Christophe Prud'homme wrote:

> Hi,
>
> lots of Linux projects use autoconf out there
> so being able to check corelinux existence using autoconf
> would be nice. Unfortunately autoconf doesn't support well
> C++ in the sense that to check libs it uses a m4 macro
> AC_CHECK_LIB this way
>
> AC_CHECK_LIB(cl++, ACCheckCoreLinux,[
> CXXFLAGS="${CXXFLAGS} -I/usr/include/corelinux"
> LDFLAGS="${LDFLAGS} "
> LIBS="${LIBS} -lcl++"
> ],[
>  echo "You need to install corelinux. see http://corelinux.sourceforge.net"
>  exit;
> ],)
>
> where cl++ is corelinux lib and ACCheckCoreLinux some symbol to check in cl++
> but the c++ mangler won't create the symbol ACCheckCoreLinux(more likely
> ACCheckCoreLinux__Fv) and AC_CHECK_LIB will create a C program
>
> char ACCheckCoreLinux();
>
> int main() {
> ACCheckCoreLinux()
> ; return 0; }
>
> and the above test will fail :(
> that is bad !
>
> So people have to create their own checking m4 macros for corelinux
> or bypass the checking of corelinux existence.
>
> We can help them by proving this symbol in corelinux
> by defining this dummy function using extern "C"
>
> extern "C" {
>   int
>   ACCheckCoreLinux()
>   {
>     return 1;
>   }
>
> and put it in libcl++
> and yes it should be documented in the Developper manual
> so that any autoconf user will be very happy. (see the macro above)
>
> well I have already done it in my cvs copy.
>
> comments?

Just put it into it's own module in the src/classlib/corelinux , like where we may
end up putting _init and so on, call it corelinux.cpp and viola if it is not too
late.

>
>
> it seems I like long mails recently :)
> C.
>
> --
> Christophe Prud'homme                |
> MIT, 77, Mass Ave, Rm 3-243          | He that breaks a thing to find out
> Cambridge MA 02139                   | what it is has left the path of wisdom.
> Tel (Office) : (00 1) (617) 253 0229 | -- J.R.R. Tolkien
> Fax (Office) : (00 1) (617) 258 8559 |
> http://augustine.mit.edu/~prudhomm   |
>                           Following the hacker spirit
>
> _______________________________________________
> Corelinux-develop mailing list
> Cor...@li...
> http://lists.sourceforge.net/mailman/listinfo/corelinux-develop

Re: [Corelinux-develop] including corelinux in a project with autoconf

[Christophe Prud'h. <pru...@MI...>]

    Frank> Just put it into it's own module in the src/classlib/corelinux , like where we may end up
    Frank> putting _init and so on, call it corelinux.cpp and viola if it is not too late.
Ok I did it 
I added also some documentation(doxygen) for this function in the code 
like the autoconf macro and I will update the developper manual

regards
C.

-- 
 Christophe Prud'homme                | Pierre: Je suis désolé Thérèse, je ne
 MIT, 77, Mass Ave, Rm 3-243          |         sais pas ce qui m'a pris...
 Cambridge MA 02139                   |         c'est une catastrophe.
 Tel (Office) : (00 1) (617) 253 0229 | Thérèse: Ce n'est rien Pierre,
 Fax (Office) : (00 1) (617) 258 8559 |          je n'ai rien senti....
 http://augustine.mit.edu/~prudhomm   | -- Le Pere Noel est une ordure
                          Following the hacker spirit

Re: [Corelinux-develop] including corelinux in a project with autoconf

[Frank V. C. <fr...@co...>]

You on another roll tonight? :)

Christophe Prud'homme wrote:

>     Frank> Just put it into it's own module in the src/classlib/corelinux , like where we may end up
>     Frank> putting _init and so on, call it corelinux.cpp and viola if it is not too late.
> Ok I did it
> I added also some documentation(doxygen) for this function in the code
> like the autoconf macro and I will update the developper manual
>
> regards
> C.
>
> --
>  Christophe Prud'homme                | Pierre: Je suis désolé Thérèse, je ne
>  MIT, 77, Mass Ave, Rm 3-243          |         sais pas ce qui m'a pris...
>  Cambridge MA 02139                   |         c'est une catastrophe.
>  Tel (Office) : (00 1) (617) 253 0229 | Thérèse: Ce n'est rien Pierre,
>  Fax (Office) : (00 1) (617) 258 8559 |          je n'ai rien senti....
>  http://augustine.mit.edu/~prudhomm   | -- Le Pere Noel est une ordure
>                           Following the hacker spirit
>
> _______________________________________________
> Corelinux-develop mailing list
> Cor...@li...
> http://lists.sourceforge.net/mailman/listinfo/corelinux-develop

Re: [Corelinux-develop] including corelinux in a project with autoconf

[Christophe Prud'h. <pru...@MI...>]

    Frank> You on another roll tonight? :) Christophe Prud'homme wrote:
Nope I have my laundry to do
I will leave around 8 or 9


do you have a description of the examples like for example
ex1 is using this pattern or/and this pattern  ?

and with the number of examples we should put the description
in README.examples which is in debian dir or elsewhere

in doxygen there is a way to include examples
and it would be nice to have that
(see the \include macro)

C.

Re: [Corelinux-develop] including corelinux in a project with autoconf

[Frank V. C. <fr...@co...>]

Christophe Prud'homme wrote:
> 
>     Frank> You on another roll tonight? :) Christophe Prud'homme wrote:
> Nope I have my laundry to do
> I will leave around 8 or 9
> 
> do you have a description of the examples like for example
> ex1 is using this pattern or/and this pattern  ?
> 
> and with the number of examples we should put the description
> in README.examples which is in debian dir or elsewhere
> 
> in doxygen there is a way to include examples
> and it would be nice to have that
> (see the \include macro)
> 
> C.
> 
> _______________________________________________
> Corelinux-develop mailing list
> Cor...@li...
> http://lists.sourceforge.net/mailman/listinfo/corelinux-develop

All the docs for the examples are in the code itself.
Usually the main exampXX.cpp has the overview of what was being,
attempted to, achieve.

-- 
Frank V. Castellucci
http://corelinux.sourceforge.net
OOA/OOD/C++ Standards and Guidelines for Linux
http://PythPat.sourceforge.net
Pythons Pattern Package

[Corelinux-develop] .spec file

[Christophe Prud'h. <pru...@MI...>]

I have a .spec file working now but it is not yet complete
it seems that rpm is working fine under debian
I have only libcorelinux and libcorelinux-dev so far

There is a new corelinux.spec.in file in corelinux root dir.
I will update tomorrow after futher testing.

regards
C.

-- 
  Christophe Prud'homme                  |
  MIT, 77, Mass Ave, Rm 3-243            |   Virtue would go far if ...
  Cambridge MA 02139                     |   vanity did not keep it company.
  Tel (Office) : (00 1) (617) 253 0229   |   -- La Rochefoucauld
  Fax (Office) : (00 1) (617) 258 8559   |
  http://augustine.mit.edu/~prudhomm     |
                          Following the hacker spirit

Re: [Corelinux-develop] .spec file

[Frank V. C. <fr...@co...>]

Christophe Prud'homme wrote:
> 
> I have a .spec file working now but it is not yet complete
> it seems that rpm is working fine under debian
> I have only libcorelinux and libcorelinux-dev so far
> 
> There is a new corelinux.spec.in file in corelinux root dir.
> I will update tomorrow after futher testing.
> 
> regards
> C.

Ok, in the meantime I will be applying the patch that was submitted and
start getting the foundations down for the Library management. 

-- 
Frank V. Castellucci