Re: PGI and C++ templates

2005-03-07 Thread Ralf Wildenhues
Sorry to self-followup. Another thing came to mind: * Ralf Wildenhues wrote on Sat, Mar 05, 2005 at 05:10:31PM CET: > * Jeff Squyres wrote on Sat, Mar 05, 2005 at 01:07:11AM CET: > > > You must now do an extra pre-link step to instantiate all the templates > > used in this library, putting all

Re: PGI and C++ templates

2005-03-07 Thread Jeff Squyres
On Mar 5, 2005, at 11:10 AM, Ralf Wildenhues wrote: For each source file in the library, compile it: $ pgCC -c --one_instantiation_per_object $(YOUR_FLAGS) file.cc Can we issue the `--one_instantiation_per_object' for all C++ source, not just the source with templates in it? I don't see a problem w

Re: PGI and C++ templates

2005-03-07 Thread Jeff Squyres
On Mar 7, 2005, at 3:07 AM, Ralf Wildenhues wrote: Achive or build the shared library as before, except you must include the new hidden templates in the Template.dir directory: $ ar qv lib_mylib.a Template.dir/*.o file1.o file2.o etc. At the moment, Template.dir/ is not cleaned by `make clean'. Th

Re: PGI and C++ templates

2005-03-07 Thread trs
Engineering can confirm 1. You should use the --instantiation_dir flag to keep separate instantiation directories for each library. 2. You should always clean the Template.dir with any changes to the associated library templates. regards, dave > On Mar 7, 2005, at 3:07 AM, Ralf Wild