[M3devel] quake c_source, gcc -I directive

Daniel Alejandro Benavides D. dabenavidesd at yahoo.es
Sun Mar 25 01:07:44 CET 2012


Hi all:
Maybe you need to create a package for that thing there /sw/include/event and create a symbolic link to it named src and compile and ship it.
Then you would import the package as everything. Wouldn't it? 

Thanks in advance

--- El sáb, 24/3/12, Dragiša Durić <dragisha at m3w.org> escribió:

> De: Dragiša Durić <dragisha at m3w.org>
> Asunto: Re: [M3devel] quake c_source, gcc -I directive
> Para: "Daniel Alejandro Benavides D." <dabenavidesd at yahoo.es>
> CC: "m3devel" <m3devel at elegosoft.com>
> Fecha: sábado, 24 de marzo, 2012 18:41
> c_source("file") will compile file.c
> in same directory as m3makefile with that line is. And put
> object in ../$TARGET/file.o
> 
> My question is, can I dd -I/sw/include so if my source has
> 
> #include <event2/event.h>
> 
> It will be found in /sw/include/event2/event.h
> 
> Of course, /usr/include, for system .h's, should work at
> same time.
> 
> dd
> 
> 
> On Mar 25, 2012, at 12:37 AM, Daniel Alejandro Benavides D.
> wrote:
> 
> > Hi all:
> > I thought the c_source file had to be named in the same
> way your modula-3 sources (src), but for any other purposes
> like finding utilities inside your src tree src/D
> > But if that's not the implementation you need but to
> link against I had to actually call the var outside the
> Modula-3 environment to override it in Modula-3 system
> linker.
> > 
> > 
> > Thanks in advance
> > 
> > --- El sáb, 24/3/12, Dragiša Durić <dragisha at m3w.org>
> escribió:
> > 
> >> De: Dragiša Durić <dragisha at m3w.org>
> >> Asunto: [M3devel] quake c_source, gcc -I directive
> >> Para: "m3devel" <m3devel at elegosoft.com>
> >> Fecha: sábado, 24 de marzo, 2012 17:12
> >> Anybody worked out an easy method
> >> resembling import_lib() to inform C compiler where
> to find
> >> include files in case it is not /usr/include? Like
> when I am
> >> using fink on a Mac, for example.
> >> 
> >> TIA,
> >> dd
> >> 
> >> 
> 
> 



More information about the M3devel mailing list