betajaen
08-03-2008 11:21:35
It has always been assumed when I start giving out stable releases of NxOgre again I would provide a pre-compiled version of the library.
Well, I've started to seriously consider doing it again; With a twist.
- The entire SDK; would be three files: NxOgre.h, NxOgre.dll, NxOgre.lib. You download those, and the PhysX SDK. Once your application is complete you copy NxOgre.dll and PhysXLoader.dll to your application folder.
- NxOgre.h is a merging of all of the NxOgre headers into one.
- No references to PhysX is needed or required; no adding include/linker directories to the application project settings or adding the PhysX libs either.
- All protected/private and variables of the NxOgre classes are not in the header file.
- There are no references to PhysX in the header file; all data types are Ogre(Vector3, Quaternion) or NxOgre(float3,float4).
- There will be no by passing NxOgre to get at PhysX, i.e. You can't get at an NxActor and do something to it.
- It will be almost "plug and play".
Well?
Well, I've started to seriously consider doing it again; With a twist.
- The entire SDK; would be three files: NxOgre.h, NxOgre.dll, NxOgre.lib. You download those, and the PhysX SDK. Once your application is complete you copy NxOgre.dll and PhysXLoader.dll to your application folder.
- NxOgre.h is a merging of all of the NxOgre headers into one.
- No references to PhysX is needed or required; no adding include/linker directories to the application project settings or adding the PhysX libs either.
- All protected/private and variables of the NxOgre classes are not in the header file.
- There are no references to PhysX in the header file; all data types are Ogre(Vector3, Quaternion) or NxOgre(float3,float4).
- There will be no by passing NxOgre to get at PhysX, i.e. You can't get at an NxActor and do something to it.
- It will be almost "plug and play".
Well?