Home » U++ Library support » U++ Core » NTL and C4251
Re: NTL and C4251 [message #2756 is a reply to message #2755] |
Mon, 24 April 2006 16:27 |
|
mirek
Messages: 13976 Registered: November 2005
|
Ultimate Member |
|
|
jmansion wrote on Mon, 24 April 2006 10:04 | >TheIDE has specific hacks to compile process that makes those
>ugly declspec issues for importing/exporting stuff unnecessary
>(EXPORTS are automatically generated, just like in linux/.so -
>no explicit export/import declarations are necessary).
Oh - I'd hardly call the situation on Linux ideal, hence the work the gcc team has been doing to make control of visibility much easier and the performance issues seen in OOo and KDE.
|
I agree that performance sucks with dynamic loading of .so. However, I think this is rather the problem of that specific implementation than the problem of visibility only.
In any case, standalony binary (like one produced by U++) beats them all
Quote: |
>Anyway, to tell the truth, U++ is designed to provide
>standalone executables, no .dlls at all.
Ouch. That's really a big disadvantage - it cuts out the use of SWIG to help automate subsystem testing etc or to provide services to JNI, P/Invoke or even to dynamically load extensions. I know I've typically released monolithic in-house binaries built static, but I'd not want to be forced to do this.
|
Well, the real meaning of standalone here is that you can ship U++ binary without any aditional .dll and it works on everything since Win95 or on most current Linux 386 distros. Anyway, on Linux, the build in fact is shared (against a limited number of system .so - namely glibc, stdc++, xlib and xft).
You can however use 3rd party .dlls, you can build .dlls (even OLE/COM components), and you can even build in "SO" mode where all library subsystems are build as dll.
Quote: |
And that's probably answered whether I could move to U++ as my main development env.
|
Well, as always, you cannot satisfy everybody.... The mission goals are low development / maintainance costs. DLL hell does not contribute to either
Mirek
|
|
|
|
|
NTL and C4251
By: jmansion on Mon, 24 April 2006 14:26
|
|
|
Re: NTL and C4251
By: mirek on Mon, 24 April 2006 15:26
|
|
|
Re: NTL and C4251
By: jmansion on Mon, 24 April 2006 15:34
|
|
|
Re: NTL and C4251
By: unodgs on Mon, 24 April 2006 19:29
|
|
|
Re: NTL and C4251
By: mirek on Mon, 24 April 2006 21:29
|
|
|
Re: NTL and C4251
By: unodgs on Mon, 24 April 2006 22:44
|
|
|
Re: NTL and C4251
By: mirek on Mon, 24 April 2006 22:49
|
|
|
Re: NTL and C4251
By: jmansion on Tue, 25 April 2006 10:23
|
|
|
Re: NTL and C4251
By: mirek on Tue, 25 April 2006 10:45
|
|
|
Re: NTL and C4251
By: unodgs on Tue, 25 April 2006 13:54
|
|
|
Re: NTL and C4251
By: jmansion on Tue, 25 April 2006 14:07
|
|
|
Re: NTL and C4251
By: mirek on Tue, 25 April 2006 14:20
|
|
|
Re: NTL and C4251
By: jmansion on Tue, 25 April 2006 14:33
|
|
|
Re: NTL and C4251
By: mirek on Tue, 25 April 2006 15:03
|
|
|
Re: NTL and C4251
By: jmansion on Tue, 25 April 2006 15:19
|
|
|
Re: NTL and C4251
By: unodgs on Tue, 25 April 2006 15:43
|
|
|
Re: NTL and C4251
By: jmansion on Tue, 25 April 2006 16:06
|
|
|
Re: NTL and C4251
By: mirek on Tue, 25 April 2006 20:10
|
|
|
Re: NTL and C4251
By: jmansion on Wed, 26 April 2006 10:02
|
|
|
Re: NTL and C4251
By: mirek on Wed, 26 April 2006 10:10
|
|
|
Re: NTL and C4251
By: jmansion on Tue, 25 April 2006 10:17
|
|
|
Re: NTL and C4251
By: jmansion on Mon, 24 April 2006 16:04
|
|
|
Re: NTL and C4251
By: mirek on Mon, 24 April 2006 16:27
|
|
|
Re: NTL and C4251
|
|
|
Re: NTL and C4251
By: mirek on Tue, 25 April 2006 09:45
|
|
|
Re: NTL and C4251
|
|
|
Re: NTL and C4251
By: mirek on Tue, 25 April 2006 10:41
|
|
|
Re: NTL and C4251
By: jmansion on Tue, 25 April 2006 10:26
|
Goto Forum:
Current Time: Fri May 10 17:48:49 CEST 2024
Total time taken to generate the page: 0.03022 seconds
|