canusx / caelum Goto Github PK

Moon phase should make a "D" when moon is growing to "full" and a "C" when 
going to black moon (there's a french sentence saying that "the moon is a 
liar", cause when it grew it make a D like Decrease, and when it goes to black 
it make a C like inCrease (or like "Croissant" in french)).
Instead of that, it allways makes a D (it's true for nord positions from 
equator, the moon is not a liar in south hemisphere, as phases are inversed ;) 
).
I Did not try for the moment if the phases are inversed while feeding Caelum 
with south hemisphere positions.
I'll check how it works in Caelum.

What steps will reproduce the problem?
1. Build Caelum in Visual Studio

What is the expected output? What do you see instead?

0 errors, 0 warnings.  Most (if not all) of the warnings involve Microsoft's 
tightening of data loss warnings when converting from double to float.  Most 
(if not all) of these warnings in Caelum are spurious (with the notable 
exception of astronomy routines that may require high accuracy).

What version of the product are you using? On what operating system?

0.6 on Win32

Please provide any additional information below.

#pragma suppression of the warnings would be acceptable, but suffixing all 
numeric constants with the appropriate 'f' code is probably preferable.

In Ogre 1.8-RC the field ms_Singleton is now named msSingleton in 
Ogre::Singleton class.

Can you please provide a CaelumPlugin class with Ogre version macro to select 
the right field.

Thanks,
Robert

What steps will reproduce the problem?
1. Run CMake (or cmake-gui) in the Caelum root directory.
2. Configure
3. Generate

What is the expected output? What do you see instead?

The Caelum project Debug build should link against OgreMain_d.lib, not 
OgreMain.lib.

What version of the product are you using? On what operating system?

0.6 on Win32

Please provide any additional information below.

The name of the library to link against might possibly be conditional based on 
whether the Ogre SDK is detected or not.  If Ogre is found but does not appear 
to include the full SDK hierarchy, linking should perhaps look for the release 
build.

There is some argument to be made that Caelum should link against a release 
build of Ogre regardless of the Caelum build, for speed purposes.  In my 
experience this does not work.  Your application will experience random 
crashes.  Possibly there is a way to successfully build a valid debug build 
against a release build library (obviously there has to be a way, or linking to 
system libraries wouldn't work), but I have yet to see a successful 
configuration involving Ogre.

Caelum HDR almost worked.  It seems more likely to be completed if the partial 
implementation is included in the migrated repository.

What steps will reproduce the problem?
1. Run Cmake (or cmake-gui) in the Caelum root folder.
2. Configure
3. Generate

What is the expected output? What do you see instead?

Expected output is vcproj files, included in the sln file, for the CaelumDemo 
and CaelumLab applications.  What you get instead is no mention of either 
application.

What version of the product are you using? On what operating system?

0.6 on Win32

Currently the library name is missing in the installed pkgconfig file because 
"LIBNAME" is not set. The attached patch fixes building of Caelum.pc from 
Caelum.pc.in.

I need to apply the attached patch to build caelum against OGRE 1.9 on an Arch 
Linux installation.

What steps will reproduce the problem?
1. Run CMake (or cmake-gui) in the Caelum root
2. Configure
3. Generate

What is the expected output? What do you see instead?

Expected output is vcproj files that include valid paths to Ogre's include and 
lib directories.

What you get instead is invalid relative paths to Ogre that point nowhere.

What version of the product are you using? On what operating system?

0.6 on Win32

Please provide any additional information below.

What steps will reproduce the problem?
1. Integrate Caelum into an Ogre 1.7.1 or above application.
2. Run the application.

What is the expected output? What do you see instead?

The expected output is success messages in the Ogre.log file mentioning loading 
and compiling Caelum's shaders.  What happens instead are fatal compile errors.

What version of the product are you using? On what operating system?

0.6 on Win32

Please provide any additional information below.

The Cg authors apparently tightened up Cg's handling of preprocessor directives 
in fragment programs.  Oddly enough this does not appear to apply to vertex 
programs.  The attached patch modifies only the directives present in the 
fragment programs, allowing a successful shader compilation under Ogre.  It may 
not go far enough, especially if the Cg authors further tighten preprocessor 
behavior.

What steps will reproduce the problem?
1. Run Cmake (or cmake-gui) in the Caelum root directory.
2. Configure
3. Generate

What is the expected output? What do you see instead?

The expected output is a solution file that disables the documentation project 
by default.  What you see instead is a project enabled by default.

What version of the product are you using? On what operating system?

0.6 on Win32

Here come the file containing the new CMake system I made for Caelum (I had 
some issues with symbol export under linux, so I rewrite one based on CMake 
code I know it works on those two platforms, no mac to test).

What steps will reproduce the problem?
1. Run Cmake (or cmake-gui) in the Caelum root directory.
2. Configure
3. Generate

What is the expected output? What do you see instead?

Expected output is a single documentation project.  What you get instead are 
two different projects.  Since there is no non-doxygen documentation, there 
should be no doc project.

What version of the product are you using? On what operating system?

0.6 on Win32

Please provide any additional information below.

If you want to follow the pattern many other libraries use, there should also 
not be a doxygen project.  The name is normally api-docs.