Hi Simon,
Sometimes the ABI will change between major compiler revisions, so you need to
indicate that in the package name.
For Visual studio, the libraries are incompatible 6,7 & 8.
- and actually service packs too... This is an FAQ, the Win32
dependencies are built for VC8sp1, if someone
2009/1/14 Jean-Sébastien Guay :
> Hi Mattias,
>
>> 1. When building static libraries - should we indicate this in the
>> package filename? e.g.
>> libopenscenegraph-dev-2.x.y-win32-x86-vc80-Release-static.tar.gz ?
>
> I would say yes, otherwise how do we separate the static and dynamic builds?
>
>>
Hi J-S,
On 1/14/09, Jean-Sébastien Guay wrote:
> Hi Mattias,
>
>> 1. When building static libraries - should we indicate this in the
>> package filename? e.g.
>> libopenscenegraph-dev-2.x.y-win32-x86-vc80-Release-static.tar.gz ?
>
> I would say yes, otherwise how do we separate the static and dyn
Hi Mattias,
1. When building static libraries - should we indicate this in the
package filename? e.g.
libopenscenegraph-dev-2.x.y-win32-x86-vc80-Release-static.tar.gz ?
I would say yes, otherwise how do we separate the static and dynamic builds?
2. For msvc OsgCPack.cmake detect the compiler
Hi all,
I have done some more testing of the packaging and have a new
submission on hold that has fixes for NMake generators and detection
of service pack 1 for msvc80. During testing some additional questions
came up:
1. When building static libraries - should we indicate this in the
package fil
5 matches
Mail list logo
