Hello Steven, Is there anyway to not include some definitions in header to delay instantiation for use with explicit template instantiations in specific translation units with type_erasure? I have a CORBA library which uses type_erasure for each interface defined in IDL. The problem is that if I include too many #include's for the precompiled headers which use type_erasure, then the compiler ends up consuming too much memory (>10GB), which makes it unfit for 32bit compilers which can use at most 3GB. Regards, -- Felipe Magno de Almeida
AMDG On 06/09/2013 01:50 PM, Felipe Magno de Almeida wrote:
Hello Steven,
Is there anyway to not include some definitions in header to delay instantiation for use with explicit template instantiations in specific translation units with type_erasure?
No not really. You could theoretically split off the instantiations of /concept/<T>::apply, but I don't know how much that would help.
I have a CORBA library which uses type_erasure for each interface defined in IDL. The problem is that if I include too many #include's for the precompiled headers which use type_erasure, then the compiler ends up consuming too much memory (>10GB), which makes it unfit for 32bit compilers which can use at most 3GB.
In Christ, Steven Watanabe
On Sun, Jun 9, 2013 at 7:25 PM, Steven Watanabe
AMDG
Hi Steven,
On 06/09/2013 01:50 PM, Felipe Magno de Almeida wrote:
Hello Steven,
Is there anyway to not include some definitions in header to delay instantiation for use with explicit template instantiations in specific translation units with type_erasure?
No not really. You could theoretically split off the instantiations of /concept/<T>::apply, but I don't know how much that would help.
I'm trying to use your template profile from https://github.com/boost-vault/Tools. It works with boost-build in boost 1.46.1, but not for >= 1.50.0. It seems the action (gcc.)compile.c++.preprocess is not overriden then. I'm using the same bjam(from trunk) for both boost-builds.
I have a CORBA library which uses type_erasure for each interface defined in IDL. The problem is that if I include too many #include's for the precompiled headers which use type_erasure, then the compiler ends up consuming too much memory (>10GB), which makes it unfit for 32bit compilers which can use at most 3GB.
In Christ, Steven Watanabe
Regards, -- Felipe Magno de Almeida
participants (2)
-
Felipe Magno de Almeida -
Steven Watanabe