I agree unfortunately. On Sep 6, 2011 6:29 PM, "Jordan Wilberding" <[email protected]> wrote: > After playing around a bit with getting it to build on my system, I think we > are just going to have to go with autotools. It is no fun, I know, but I > don't see the current way being very reliable. > > On Mon, Sep 5, 2011 at 2:48 PM, Eric Merritt <[email protected]> wrote: > >> The caveats are that we arent using the libarchive build system at all >> we are using our own. So I have no idea if we are defining everything >> we should or shouldn't and it would be rough to know what should be >> there until it breaks. That and the bad smell of duplicating another >> repo in our own. >> >> On Mon, Sep 5, 2011 at 11:39 AM, Jordan Wilberding >> <[email protected]> wrote: >> > What are the caveats? >> > >> > On Mon, Sep 5, 2011 at 12:14 PM, Eric Merritt <[email protected]> >> > wrote: >> >> >> >> I am playing with removing the deps directory, well at least >> >> libarchive. The problem I am running into is that libarchive uses >> >> libtool to make its libraries which is not compatible with the normal >> >> non-libtool crap and waf does not support libtool well at all. >> >> >> >> I am pretty sure removing libarchive from being included in the app >> >> (and libz which would be required as well) is a good thing. A very >> >> good thing. However, I dont think it can easily be done with waf. That >> >> means converting to something else. Probably autotools hate, hate, >> >> hate them though I do. >> >> >> >> The other option is to leave libarchive in the dependencies, add libz >> >> and continue on. The upside there is it already works though with a >> >> bunch of caveats. I am a bit stuck as to the best way to go so I >> >> thought I would solicit opinions. >> >> >> >> Eric >> >> >> >> -- >> >> You received this message because you are subscribed to the Google >> Groups >> >> "erlware-dev" group. >> >> To post to this group, send email to [email protected]. >> >> To unsubscribe from this group, send email to >> >> [email protected]. >> >> For more options, visit this group at >> >> http://groups.google.com/group/erlware-dev?hl=en. >> >> >> > >> > -- >> > You received this message because you are subscribed to the Google Groups >> > "erlware-dev" group. >> > To post to this group, send email to [email protected]. >> > To unsubscribe from this group, send email to >> > [email protected]. >> > For more options, visit this group at >> > http://groups.google.com/group/erlware-dev?hl=en. >> > >> >> -- >> You received this message because you are subscribed to the Google Groups >> "erlware-dev" group. >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]. >> For more options, visit this group at >> http://groups.google.com/group/erlware-dev?hl=en. >> >> > > -- > You received this message because you are subscribed to the Google Groups "erlware-dev" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to [email protected]. > For more options, visit this group at http://groups.google.com/group/erlware-dev?hl=en. >
-- You received this message because you are subscribed to the Google Groups "erlware-dev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/erlware-dev?hl=en.
