corelinux-develop Mailing List for CoreLinux++ (Page 37)

Brought to you by: frankc, frankiec

corelinux-develop — Developer centric mail list for CoreLinux++

You can subscribe to this list here.

2000	Jan	Feb	Mar	Apr	May	Jun	Jul (144)	Aug (209)	Sep (117)	Oct (44)	Nov (41)	Dec (1)
2001	Jan (14)	Feb (64)	Mar (25)	Apr (35)	May (29)	Jun (6)	Jul (7)	Aug	Sep (12)	Oct (6)	Nov	Dec (1)
2002	Jan	Feb	Mar	Apr	May (1)	Jun (1)	Jul	Aug	Sep	Oct	Nov	Dec
2003	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep	Oct	Nov (1)	Dec
2004	Jan (1)	Feb	Mar	Apr	May (1)	Jun	Jul	Aug	Sep	Oct (1)	Nov	Dec
2006	Jan (7)	Feb (5)	Mar (2)	Apr (1)	May (9)	Jun (11)	Jul (9)	Aug (5)	Sep (7)	Oct	Nov	Dec (9)
2007	Jan (3)	Feb (5)	Mar (2)	Apr (5)	May (1)	Jun (1)	Jul (5)	Aug (16)	Sep (7)	Oct (8)	Nov (8)	Dec (2)
2008	Jan (4)	Feb (7)	Mar (27)	Apr (26)	May (28)	Jun (17)	Jul (38)	Aug (13)	Sep (17)	Oct (12)	Nov (37)	Dec (51)
2009	Jan (41)	Feb (19)	Mar (30)	Apr (43)	May (138)	Jun (111)	Jul (76)	Aug (27)	Sep (28)	Oct (33)	Nov (11)	Dec (18)
2010	Jan (3)	Feb (5)	Mar (40)	Apr (51)	May (74)	Jun (76)	Jul (46)	Aug (41)	Sep (26)	Oct	Nov	Dec
2012	Jan	Feb (1)	Mar	Apr	May	Jun	Jul	Aug	Sep	Oct	Nov	Dec

Flat | Threaded

<< < 1 .. 35 36 37 38 39 40 > >> (Page 37 of 40)

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

From: Frank V. C. <fr...@co...> - 2000-07-27 21:04:43

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

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

From: Christophe Prud'h. <pru...@MI...> - 2000-07-27 20:56:24

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