Re: [chrony-dev] Build scripts.

[Jonathan Cameron <jic23@xxxxxxxxx>]

Miroslav Lichvar wrote:
> On Tue, Nov 03, 2009 at 06:35:43PM +0000, Jonathan Cameron wrote:
>>> Can you elaborate on what is needed to build it on the system?
>> Sure. The current problem is that the script is not making it easy to pass in
>> the linker parameter --hash-style=gnu. I can slip it in by making sure LDFLAGS
>> are explicitly used.
> 
> That should be easy to fix. Thanks for the patch :).
> We should add also CPPFLAGS support while we are it.
Yup that makes sense (and I see you've already pushed the changes. Thanks)
>> I'd agree if chrony didn't already have a lot of rather specific hacks.
> 
> Would the hacks disappear if we switched to autotools?
Some would remain, but hopefully you'd move more to an include relevant headers if
present rather than OS specific.  Should cut down on the number of issues.
 
>> Also, if those are the only support systems, then there is a fair bit of cleanup
>> to do removing old windows support amongst other things.
> 
> The documentation states that only chronyc builds in cygwin, I never
> tried it though.
> 
>> The question really comes down to whether it is easier to maintain custom
>> scripts and fix build trouble when it occurs, or do a clean set of autotools
>> scripts that 'more or less' should work for anything anyone throws at them.
>> This is particularly relevant for any automated builds where a lot of compile
>> settings may vary.
> 
> Based on my previous experiences with autotools I'd say maintaing the
> current scripts is really the easier option. The build is
> straigthforward, there are no shared objects or anything complicated.
> Most of the portability related code is in sys_* files anyway.
> 
> If there is anything else that breaks your build, I'll do my best to
> fix it. 
thanks.

Jonathan

---
To unsubscribe email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "unsubscribe" in the subject.
For help email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "help" in the subject.
Trouble?  Email listmaster@xxxxxxxxxxxxxxxxxxxx.