callforsanity / caelum Goto Github PK
View Code? Open in Web Editor NEWCMake port of caelum for Ogre3D
CMake port of caelum for Ogre3D
INTRODUCTION Caelum is an open-source sky rendering library for OGRE. For more information see the big Caelum thread on the ogre forum: http://www.ogre3d.org/phpBB2/viewtopic.php?t=24961 The thread is very long; you should try reading it backwards. There is also a page on the ogre wiki (might be out of date): http://www.ogre3d.org/wiki/index.php/Caelum Caelum is distributed under the LGPL. What this basically means is that you can do what you please but you should send any changes back. The forum is the best place to do this. COMPILING Compiling on windows is easiest. You need Visual Studio 2005 or 2008 and the Ogre 1.4 SDK installed. Just open the project files and click build; it should work. A SConstruct file is provided for linux. Making it work required writing ogre.cfg files and such and is harder than on windows. You should be able to get it working if you have some experience building software for linux. USAGE See CaelumDemo's source code; it should contain some minimal initialisation and tweaking. CaelumLab is more complicated and can be used to visually tweak different sky elements. There is no Caelum "SDK"; the recommended way to use it is to build it yourself. DOCUMENTATION Caelum's code has plenty of comments in doxygen format. It is not known if building doxygen documentation actually works; but you can at least read the comments. /* vim: set nocin noai tw=78 spell: */
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.
Original issue reported on code.google.com by [email protected]
on 11 May 2011 at 10:58
Attachments:
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.
Original issue reported on code.google.com by [email protected]
on 11 May 2011 at 10:19
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).
Original issue reported on code.google.com by [email protected]
on 8 Jun 2011 at 10:25
Attachments:
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
Original issue reported on code.google.com by [email protected]
on 11 May 2011 at 10:21
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.
Original issue reported on code.google.com by [email protected]
on 11 May 2011 at 10:25
I need to apply the attached patch to build caelum against OGRE 1.9 on an Arch
Linux installation.
Original issue reported on code.google.com by [email protected]
on 6 Nov 2014 at 12:03
Attachments:
Caelum HDR almost worked. It seems more likely to be completed if the partial
implementation is included in the migrated repository.
Original issue reported on code.google.com by [email protected]
on 11 May 2011 at 10:41
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.
Original issue reported on code.google.com by [email protected]
on 11 May 2011 at 10:34
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.
Original issue reported on code.google.com by [email protected]
on 31 May 2011 at 7:09
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.
Original issue reported on code.google.com by [email protected]
on 11 May 2011 at 10:38
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.
Original issue reported on code.google.com by [email protected]
on 28 Dec 2012 at 10:20
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
Original issue reported on code.google.com by [email protected]
on 11 May 2011 at 10:26
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
Original issue reported on code.google.com by [email protected]
on 22 Jan 2012 at 1:29
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.