Scolring - Forum

Yep maybe... if i succeed to make it work...
Even my "simple" ogre only sample do not work for the moment...

He, and by the way, merry christhmas (i know i'm late) !

Hey!

Yep, i know for this LNK4098 warning (http://msdn.microsoft.com/en-us/library … 71%29.aspx), and we got many solution to resolves that:
1) Like you said, rewrite the FindZLib.cmake script. I did not choose this solution for now, cause i want to use cmake officials scripts whenever it's possible (less maintenance work for me , and multiplatforms scripts).
2) Add a "/NODEFAULTLIB" statement to preprocessor flags. The problem for that it that's not easy to add some definitions specially for a compilation target (in our case, debug) with cmake.
3) Ignore this warning, as we do not really need to have zlib debug symbols (in my opinion). We could eventually use 'pragma ignore warning', or nothing at all...
Initially, I arbitrary choose the 3rd solution, as for me this warning is not critical, and there's drawbacks for the others solution, but, i could eventually switch to solution 1.

Yep, those lines are unuseful here (it's a "for all projects" include and libs inclusion path). Should be removed.

The cmake system was initialy the one i used to compile the vm on ubuntu, so it "was" working, but do not know how that's goes now...

Hi again ^^

Zlib needs to write on the registry, cause that's the way cmake found it:
Each dependency is finded using a cmake command (check Scol/CMake/ScolDependencies.cmake): find_package(LibName)
This command use a script file named FindLibName.cmake to check where the dependency files (headers and .lib) should be found.
Lots of Findxxx scripts are installed with cmake (in Programs Files\Cmake\Share\Module if i remind well), so when they exists, i use cmake provided scripts.
If you open the FindZLIB file you'll see that it use pkglib to find zlib on unix platforms, and the registry to find it on Windows (not very clean, i must accept that, but it's the cmake official zlib Find script).
Hopes my explications are clear ^^

PS: most of other cmake "Find scripts" provide an aenvironment variable to find the root directory for a dependency, but FindJPEG.cmake and FindPNG.cmake do not provided some, so, it's mostly a hack to add "${ENV_SCOL_DEPENDENCIES_PATH}/libjpeg" to the scol cmake search path, that's not the cmake "normal way" of doing.

Hi everybody.

Lib 2D OS as been ported to Cmake.
To make it compile, you'll have to update trunk/dependencies, trunk/scol (and trunk/tools too).
You'll need to re-run setWindowsSearchPaths.bat, as there's new dependencies. I added a small text file to explain how to compile the dependencies if you are using another msvs version than 2008 (there's pre-compiled libs for msvc 2008, so no need to build them).

<edit>As Arkeon noticed me, you may have to "Delete cache" from cmake menu before generating the project</edit>
Next, launch cmake as usual.

PS: As lib2dOS is windows only, it will not appears on others platforms, but i wish i do not broke cmake scripts for unix.

Haha, you can't !!!

No, seriously, first you have to activate the scol Log: Scol Voyager, right click on the notification icon, select Configure/Advanced (not sure of the labels, me and arkeon have done so many modifications to SO3 that even ScolVoyager refuse to run for the moment), and set:

log yes
?level? ffff

There another option useful, "do not close scol window when exiting", but didn't remember where the hell it's in Scol Voyager...

With the log in the console plus the log file (in C:\Users\%AccountName%\AppData\Local\Scol Voyager\Logs), you will have some useful informations about your error.
But, if you want something like visual studio debugger, it not possible. Like in javascript, in last resort, use log text functions or dialog box functions to show your variables values.

In fact, we are currently totally refactoring the engine, so, now it starts to be structured ^^, but once this done (and it have to be done sooner as possible, to avoid this type of obsolescence), the engine api will evoluate more logically than today, with no api breaks at all. Need some time to rewrite all, but the big part is done

Thanks for the cheers

The resolution of the generated mesh is quite impressive, for photo shooted generation.

Hum, i'm think that Kenshin is right, that's an error...
And you have almost right arkeon, but in fact it's the code show there that is Ogre 1.6 specific.
It will be removed soon, but i'll commit your correction asap.

Thank you Kenshin.

<edit>This code totally confuse me, do not understand why we reconstruct the fsaa string, but can't debug it for the moment, cause to do that i'll have to come back to ogre 1.6...</edit>

Who's the stupid guy who wrote this "hello world" template?
Oups... it was me...

Just committed usmwin converted to cmake.
No problem with release, but you may remark that i added a '_d' at the end of the scol.dll for debug build, as lots of libraries does.
Goto sleep (:o wahhh), bye!

Just commited the vm5 cmake version.
Next priority will be to convert usmwin (i think it's broken, not tested, but i pretty sure cause includes directories have changed...).
I'll write a cmake tuto asap in another post.

Nodrev.