FreeRADIUS 3.0: 3rd party module build structure?

[Arran Cudbard-Bell]

On 27 Feb 2014, at 21:58, Julius Plenz <plenz at cis.fu-berlin.de> wrote:

> Hi, Alan!
> 
> * Alan DeKok <aland at deployingradius.com> [2014-02-27 22:28]:
>> Copy an "all.mk" from another module, and set the relevant flags.
>> Notice it's a *lot* simpler than before:
>> 
>> TARGET = rlm_omapi.la
>> SRCS   = rlm_omapi.c
>> TGT_CFLAGS = -I/server/dhcp/server/include -I/server/dhcp/src/isc-dhcp/bind/include
>> TGT_LDFLAGS = -L/server/dhcp/server/lib -ldhcpctl -lomapi -ldns -lisc
> 
> Yes, I got so far. But I'm developing the module in a separate
> repository outside the FreeRADIUS sources (e.g. I have ~/src/rlm_omapi
> and ~/src/freeradius). I'd like to include some makefile from the
> FreeRADIUS source tree without the need to copy my module into the
> source tree under src/modules in order to compile it there. Is that
> possible?

You can pull in the boiler make files if you really want. Else you could add it as a git submodule.

-Arran

Arran Cudbard-Bell <a.cudbardb at freeradius.org>
FreeRADIUS Development Team

FD31 3077 42EC 7FCD 32FE 5EE2 56CF 27F9 30A8 CAA2

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 881 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.freeradius.org/pipermail/freeradius-users/attachments/20140227/258d2bab/attachment.pgp>