I was initially concerned, like you, about putting such generic-sounding libraries in /usr/local/lib, but of course that’s not the full name. On the current machine (whose rust is slightly out of date, so this may not match the name you have), libstd is actually
/usr/local/lib/libstd-6c65cf4b443341b1-0.9-pre.dylib I’m not aware of any other system that adds hashes to library names like rust does, so it seems like a pretty good distinction without needing to namespace them or put “rust’ in the name. -Kevin On Nov 14, 2013, at 10:17 AM, Gaetan <[email protected]> wrote: > I speak about the file names: /usr/local/lib/libstd... And > /usr/local/lib/libextra > > Le jeudi 14 novembre 2013, Kevin Cantu a écrit : > These standard libraries are already packaged for use and documented on the > homepage. The import for std is implied, and for the second you just need > this: > extern mod extra; > > Cheers, > Kevin > > > > On Thu, Nov 14, 2013 at 9:50 AM, Gaetan <[email protected]> wrote: > > I have a question about the two files "libextra" and "libstd" that are > installed by rust compiler. > > Can they be called by any normal average program? > > If so, shouldn't we document how? > If this has no sense, I suggest to rename them to something like "libruststd" > or "librustextra" to avoid naming conflict with system libraries. We can also > move to a subdirectory of /usr/lib, like /usr/lib/rust. > > What do you think about this? > ----- > Gaetan > > > _______________________________________________ > Rust-dev mailing list > [email protected] > https://mail.mozilla.org/listinfo/rust-dev > > > > > -- > ----- > Gaetan > > > _______________________________________________ > Rust-dev mailing list > [email protected] > https://mail.mozilla.org/listinfo/rust-dev
_______________________________________________ Rust-dev mailing list [email protected] https://mail.mozilla.org/listinfo/rust-dev
