Indeed. They all have their nuances :) On Tue, Jun 4, 2019 at 4:36 PM Guy Harris <g...@alum.mit.edu> wrote:
> On Jun 4, 2019, at 2:27 PM, Bryan Christ <bryan.chr...@gmail.com> wrote: > > > Thanks for the explanation. Yes. The use of the term Library certainly > added to my confusion. I've been coding on Linux for 20 and the "proper" > way of doing things on Mac is a bit elusive to me as I stumble around. > > Yeah, it must be weird going from a system that stuffs libraries in > /usr/lib64 to a system that stuffs them in /usr/lib. :-) > > (There's no need to put 32-bit and 64-bit libraries in separate > directories if you can put the 32-bit and 64-bit versions of a library in > the same file, as you can in Darwin. > > But the real point is that every UN*X has its own quirks, and somebody > might find the UN*X with which you're most familiar to be the quirky one. > If you're going to do cross-platform UN*X programming, be prepared to have > assumptions about UN*X, made based on the platform or platforms with which > you're familiar, to be violated by some other UN*X.) -- Bryan <><
-- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake
