> one thing you can eventually try to get away with the mozconfig is
> generating it from pre-configure using CONFIGURE_ARGS, but putting the
> pre-configure target **after** including bsd.port.mk, which would
> evaluate the args from modules etc.
>
> eg set your CONFIGURE_ARGS, and at the bottom of the Makefile:
>
>   .include <bsd.port.mk>
> post-configure:
> 	# XXX copy the mozconfig header/static lines
> .for a in ${CONFIGURE_ARGS}
> 	echo "ac_add_options ${a}" >> ${MOZCONFIG}
> .endfor
>
> this might work, or not, is totally untested, and might attract dragons :)
>
> Landry


nah. i'm planning to overhaul this again on the weekend, doing away with 
mozconfig entirely, so that the logic can be made to match the ff port, 
configuring everything from there, and then CONFIGURE_ARGS will work.

the port as-is should otherwise be fine for now. CONFIGURE_ENV still 
applies correctly, irrespective of mozconfig.


-- 
Company director, Minifree Ltd
Registered in England, No. 9361826 | VAT No. GB202190462
Registered Office: 19 Hilton Road, Canvey Island, Essex SS8 9QA, UK

• OpenPGP_0x5C654067D383B1FF.asc (3K)