We looked at libuuid, but it seemed silly to add an external dependency for something that's a couple of dozen lines of code. The algorithms are documented in the relevant RFCs, so a compatible implementation is not hard.
David On 29 May 2011, at 20:54, Stefan Bidi wrote: > The reason I used libuuid is because that's what Apple uses > (http://en.wikipedia.org/wiki/Universally_unique_identifier). It was easy > enough to wrap it. I guess we could have either fallback code for people > without libuuid (in which case I'd need to create a configure script) or just > completely get rid of the dependency. Any opinions? > > Stef > > On Sun, May 29, 2011 at 2:30 PM, David Chisnall <[email protected]> wrote: > On 29 May 2011, at 20:28, Stefan Bidi wrote: > > > Do you have the uuid library installed (libuuid1 + uuid-dev on Debian)? > > This is a new dependency. The uuid_t type is defined in uuid/uuid.h, there > > should be no reason why you're getting this error if the headers are > > correctly installed. > > Please take a look at the ETUUID code. We have well-tested implementations > of the UUID generation algorithms, without introducing an external dependency. > > David > > -- > This email complies with ISO 3103 > > > _______________________________________________ > Gnustep-dev mailing list > [email protected] > https://lists.gnu.org/mailman/listinfo/gnustep-dev -- Sent from my Apple II _______________________________________________ Gnustep-dev mailing list [email protected] https://lists.gnu.org/mailman/listinfo/gnustep-dev
