Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.c++ > #67220
| From | "Chris M. Thomasson" <invalid_chris_thomasson_invalid@invalid.com> |
|---|---|
| Newsgroups | comp.lang.c++ |
| Subject | Re: Geodetic Development Tool |
| Date | 2019-07-31 02:14 -0700 |
| Organization | Aioe.org NNTP Server |
| Message-ID | <qhrm5e$lsb$1@gioia.aioe.org> (permalink) |
| References | (3 earlier) <qhpkdr$rvm$1@news.albasani.net> <qhrb89$13fc$1@gioia.aioe.org> <qhrgdv$vn6$1@dont-email.me> <qhris3$73m$1@gioia.aioe.org> <qhrkse$n0s$1@dont-email.me> |
On 7/31/2019 1:52 AM, Paavo Helde wrote: > On 31.07.2019 11:18, Chris M. Thomasson wrote: >> On 7/31/2019 12:36 AM, Paavo Helde wrote: >>> On 31.07.2019 9:08, Chris M. Thomasson wrote: >>>> On 7/30/2019 7:32 AM, Fred Killet wrote: >>>>> Yes, 20000 lines of source code with geodetic functions have their >>>>> price. However, WINDOWS programmers have the advantage to integrate >>>>> geodetic functions as a DLL. That is already possible from 500 euros. >>>>> Fred >>>> >>>> shared object files on Linux should work fine. >>> >>> It takes some knowledge and experience to prepare a binary C++ .so >>> which would work on most Linuxes, especially if it is using a lot of >>> third-party libraries. The default model in Linux is to use the >>> system-installed C++ runtimes, but there have been ABI-breaking >>> changes in those runtimes, so one just cannot compile a .so on a >>> random Linux box and hope it will work everywhere. Third-party >>> libraries with C++ interfaces will add many complications, one could >>> either use system-installed ones or package them together with your >>> own .so, both approaches have serious drawbacks. >>> >>> In short, the easiest way to install custom software (not included in >>> package manager repos) in Linux is to build it directly on the target >>> box. >>> >>> >> >> Humm... It would be wise to create the shared object API using C. The >> guts can be C++, exceptions aside for a moment... but the API would be >> all in C. A little C++ wrapping up the C shared API would work. Sound a >> little better? Plugin interface. > > Yes, this is a good approach for some C++ libraries, but requires extra > work and may hinder performance. Another good approach is to create > header-only libraries, so there is no .so to link to. > > Agreed. Sometimes, its hard to beat a pure header based lib. I am quite fond of GLM: https://glm.g-truc.net/0.9.2/api/a00001.html ;^)
Back to comp.lang.c++ | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Geodetic Development Tool killet@killetsoft.de - 2019-07-30 01:18 -0700
Re: Geodetic Development Tool "Alf P. Steinbach" <alf.p.steinbach+usenet@gmail.com> - 2019-07-30 12:44 +0200
Re: Geodetic Development Tool Öö Tiib <ootiib@hot.ee> - 2019-07-30 05:42 -0700
Re: Geodetic Development Tool Fred Killet <info_nospam_@killetsoft.de> - 2019-07-30 16:32 +0200
Re: Geodetic Development Tool "Chris M. Thomasson" <invalid_chris_thomasson_invalid@invalid.com> - 2019-07-30 23:08 -0700
Re: Geodetic Development Tool Paavo Helde <myfirstname@osa.pri.ee> - 2019-07-31 10:36 +0300
Re: Geodetic Development Tool "Chris M. Thomasson" <invalid_chris_thomasson_invalid@invalid.com> - 2019-07-31 01:18 -0700
Re: Geodetic Development Tool Paavo Helde <myfirstname@osa.pri.ee> - 2019-07-31 11:52 +0300
Re: Geodetic Development Tool "Chris M. Thomasson" <invalid_chris_thomasson_invalid@invalid.com> - 2019-07-31 02:14 -0700
Re: Geodetic Development Tool Manfred <noname@add.invalid> - 2019-07-31 14:44 +0200
Re: Geodetic Development Tool Soviet_Mario <SovietMario@CCCP.MIR> - 2019-08-02 13:59 +0200
Re: Geodetic Development Tool Öö Tiib <ootiib@hot.ee> - 2019-07-31 00:36 -0700
Re: Geodetic Development Tool Bonita Montero <Bonita.Montero@gmail.com> - 2019-07-31 10:15 +0200
Re: Geodetic Development Tool "Chris M. Thomasson" <invalid_chris_thomasson_invalid@invalid.com> - 2019-07-31 01:22 -0700
Re: Geodetic Development Tool Jorgen Grahn <grahn+nntp@snipabacken.se> - 2019-07-30 18:11 +0000
csiph-web