Jason Tishler writes:
> > Seems like that's heading in the wrong direction. Isn't there a
> > compiler switch or something we could give to make ALL global vars be
> > automatically marked DLLIMPORT? That's generally how it works on Unix
> > platforms (for example, on HPUX the -E linker switch makes these symbols
> > available to dynamically linked shlibs).
> There is a way and the PostgreSQL build is already taking advantage of
> dlltool --export-all --output-def postgres.def access/SUBSYS.o ...
> However, there is a downside to the above. Now all functions and global
> variables are exported from postgres.exe -- not just the ones that make
That's the same across all platforms though. "Sense" is something the
user can find out about.
> Unfortunately, the above still does not mitigate the need for marking
> global variables DLLIMPORT in their corresponding header files to
> prevent unresolved linker errors by clients of libpostgres.a.
What's the point of --export-all then?
Peter Eisentraut peter_e(at)gmx(dot)net http://yi.org/peter-e/
In response to
pgsql-ports by date
|Next:||From: Tom Lane||Date: 2001-01-09 18:05:13|
|Subject: Re: Cygwin PostgreSQL postmaster abort problem |
|Previous:||From: Yutaka tanida||Date: 2001-01-09 15:43:21|
|Subject: Re: (Cygwin) postmaster shutdown problem|