On 2012.05.01 22:05, Ludovic Rousseau wrote: > If the only benefit of running ./configure in autogen.sh is speed on > Windows I propose to use an opt-in option and run ./configure only on > Windows or if requested.
Speed was part of it. But we also found a few examples of autogen.sh that called on configure. > I found some references: > - glib [1] uses $NOCONFIGURE > - gst-editor [2] uses ./autogen.sh --noconfigure Glib is fairly high profile, so that's good enough for me. > If the default is to call ./configure I'd personally prefer it, as I could use not wasting additional time on Windows either having to monitor the completion of one step before manually launching the next, adding extra options or creating files each time I run a clean build, since it's by far the slowest platform when using autotools. > I would like to be able to > select the opt-out option by just (and permanently) creating a file > like .noconfigure. Sounds fair and simple to implement. Let's see what others say. By the way, do you still consider the update of version.h and the running of autotools that results as something you want to see fixed? As I said, we can move the nano into its own nano.h to avoid the issue, but I'm not sure of how important you or anybody else sees that issue right now. Regards, /Pete ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
