Development troubleshooting

Subject: Re: Development troubleshooting Tue Oct 08, 2013 3:24 pm

Building install doesn't resolve the issue, i can just copy the dlls manually now i know where they are, unless you'd like to debug my problem for future devs

EDIT: It is working, i was just using the exe put at root, the exe in dist/bin works fine and has the dlls

Subject: Re: Development troubleshooting Tue Oct 08, 2013 3:26 pm

In case it wasn't clear, you'll need to manually go into the mentioned "dist" subdirectory and start the application. I don't know of a way to comfortably do this from inside Code::Blocks.

Subject: Re: Development troubleshooting Tue Oct 08, 2013 3:29 pm

Yep, got it running! it crashes right after it fullscreens though, is that related to your syntax error?

EDIT: Didn't crash on second run. I think i read about this bug somewhere on the forums

Subject: Re: Development troubleshooting Tue Oct 08, 2013 3:36 pm

Yeah, I remember someone having similar problems that disappeared the second time around. Worked fine for me a couple of hours ago in the first run. Really weird.

Subject: Re: Development troubleshooting Tue Oct 08, 2013 3:41 pm

Yep. Anyway thanks for all the help again! i learned a lot and i'll make sure to try and help others asking for help in here if i can!

I'll check in at all the other threads and see if i can't start tinkering a bit to get myself familiar with everything!

Subject: Re: Development troubleshooting Tue Oct 08, 2013 3:45 pm

You're welcome. By the way, in the "doc" subdirectory you can find some files (those ending in "dox") that contain a bit of information about how the engine is clobbered together. You could use doxygen to generate a nice HTML version (see the FAQ for some hints) or just read the raw markup, which isn't too hideous.

If those texts are unclear anywhere, let me know and I'll fill them in where possible.

Subject: Re: Development troubleshooting Tue Oct 08, 2013 3:53 pm

Yeah i built doxygen yesterday already I wonder if it got everything tho, since i didn't have things working then!

Regarding unclear things, which forum would you like me to use? or do you have an irc or alike that you prefer?

Subject: Re: Development troubleshooting Thu Oct 10, 2013 5:08 am

crovea wrote:: Regarding unclear things, which forum would you like me to use? or do you have an irc or alike that you prefer?

I think the best option is to create a ticket over at GitHub, that's not as prone to being burried as a forum post. Our usual IRC is posted in this thread, although it's usually not very active. I'll try and be more present in there for any questions / coordination.

Subject: Re: Development troubleshooting Mon Oct 28, 2013 4:16 pm

Hi,
trying to set up my local development environment for Thrive, I have been following the readme file for a few hours now and after resolving errors on cloning / updating the submodules (had to give admin rights to git) and running the script (which was one of the few things that didn't cause errors), I am stuck getting CMake to do what it should do. I am sure that I configured it as correct as possible so far, however, CMake doesn't find something called PkgConfig, is unable to find the requested Boost libraries or header files, can't find Bullet and has trouble with a not-contained CMakeLists.txt file. As a complete novice in all of these things, I would appreciate any help to get it working!

Full error from the tiny CMake console:

Code:: The C compiler identification is GNU 4.7.3
The CXX compiler identification is GNU 4.7.3
Check for working C compiler: C:/MinGW/bin/gcc.exe
Check for working C compiler: C:/MinGW/bin/gcc.exe -- works
Detecting C compiler ABI info
Detecting C compiler ABI info - done
Check for working CXX compiler: C:/MinGW/bin/g++.exe
Check for working CXX compiler: C:/MinGW/bin/g++.exe -- works
Detecting CXX compiler ABI info
Detecting CXX compiler ABI info - done
Looking for OGRE...
OGRE_PREFIX_WATCH changed.
Could NOT find PkgConfig (missing: PKG_CONFIG_EXECUTABLE)
Found Ogre Byatis (1.8.1)
Found OGRE: optimized;C:/MinGW/OgreSDK/lib/release/libOgreMain.dll.a;debug;C:/MinGW/OgreSDK/lib/debug/libOgreMain_d.dll.a
Looking for OGRE_Paging...
Found OGRE_Paging: optimized;C:/MinGW/OgreSDK/lib/release/libOgrePaging.dll.a;debug;C:/MinGW/OgreSDK/lib/debug/libOgrePaging_d.dll.a
Looking for OGRE_Terrain...
Found OGRE_Terrain: optimized;C:/MinGW/OgreSDK/lib/release/libOgreTerrain.dll.a;debug;C:/MinGW/OgreSDK/lib/debug/libOgreTerrain_d.dll.a
Looking for OGRE_Property...
Found OGRE_Property: optimized;C:/MinGW/OgreSDK/lib/release/libOgreProperty.dll.a;debug;C:/MinGW/OgreSDK/lib/debug/libOgreProperty_d.dll.a
Looking for OGRE_RTShaderSystem...
Found OGRE_RTShaderSystem: optimized;C:/MinGW/OgreSDK/lib/release/libOgreRTShaderSystem.dll.a;debug;C:/MinGW/OgreSDK/lib/debug/libOgreRTShaderSystem_d.dll.a
OIS_PREFIX_PATH changed.
Could NOT find PkgConfig (missing: PKG_CONFIG_EXECUTABLE)
CMake Error at cmake_modules/FindBoost.cmake:1192 (message):
  Unable to find the requested Boost libraries.

  Unable to find the Boost header files. Please set BOOST_ROOT to the root
  directory containing Boost or BOOST_INCLUDEDIR to the directory containing
  Boost's headers.
Call Stack (most recent call first):
  CMakeLists.txt:88 (find_package)

CMake Warning (dev) at CMakeLists.txt:94 (add_subdirectory):
  The source directory

   C:/Filestuff/C++/Thrive/contrib/googletest

  does not contain a CMakeLists.txt file.

  CMake does not support this case but it used to work accidentally and is
  being allowed for compatibility.

  Policy CMP0014 is not set: Input directories must have CMakeLists.txt. Run
  "cmake --help-policy CMP0014" for policy details. Use the cmake_policy
  command to set the policy and suppress this warning.
This warning is for project developers. Use -Wno-dev to suppress it.

CMake Error at C:/Program Files (x86)/CMake 2.8/share/cmake-2.8/Modules/FindPackageHandleStandardArgs.cmake:108 (message):
  Could NOT find Bullet (missing: BULLET_DYNAMICS_LIBRARY
  BULLET_COLLISION_LIBRARY BULLET_MATH_LIBRARY BULLET_SOFTBODY_LIBRARY)
Call Stack (most recent call first):
  C:/Program Files (x86)/CMake 2.8/share/cmake-2.8/Modules/FindPackageHandleStandardArgs.cmake:315 (_FPHSA_FAILURE_MESSAGE)
  cmake_modules/FindBullet.cmake:70 (FIND_PACKAGE_HANDLE_STANDARD_ARGS)
  CMakeLists.txt:107 (find_package)

Configuring incomplete, errors occurred!
See also "C:/Filestuff/C++/Thrive_builds/CMakeFiles/CMakeOutput.log".

If it is of importance, my OS is Windows 7 Home Premium

(btw, crovea has already been helping me out a lot via Skype, but in this case he doesn't know a solution too)

Subject: Re: Development troubleshooting Mon Oct 28, 2013 4:23 pm

I'm also having the same errors as HariboTer on my laptop (i had other errors that were resolved on my desktop pc).

I'll add that both him and me are running windows 7.

Subject: Re: Development troubleshooting Mon Oct 28, 2013 4:57 pm

Code:: Could NOT find PkgConfig (missing: PKG_CONFIG_EXECUTABLE)

That line is normal, don't worry about it.

Code:: Unable to find the requested Boost libraries.

That one is not. Sounds like something went wrong with the setup script and screwed up the boost installation. Can you check whether the directory C:/MinGW/install/include/boost exists and contains a whole bunch of stuff? Also see if you can find files named "libboost_XYZ-mt.dll" inside C:/MinGW/install/lib.

Can you paste the output of the setup script to Pastebin? You can use the Powershell ISE (which should already be installed on Windows 7) to get a console that remembers more than 20 lines.

Code:: The source directory

C:/Filestuff/C++/Thrive/contrib/googletest

does not contain a CMakeLists.txt file.

This looks like something went wrong with the submodules (I'm seriously considering removing them and just copying the files into our repository). Is there anything inside the directory it mentions? Maybe try initializing and updating the googletest submodule once more.

Code:: Could NOT find Bullet (missing: BULLET_DYNAMICS_LIBRARY
BULLET_COLLISION_LIBRARY BULLET_MATH_LIBRARY BULLET_SOFTBODY_LIBRARY)

More errors that suggest that the setup script had trouble, but it's probably a follow-up error of the missing boost libraries, causing errors when building bullet.

Subject: Re: Development troubleshooting Mon Oct 28, 2013 7:02 pm

Nimbal wrote:: Can you check whether the directory C:/MinGW/install/include/boost exists and contains a whole bunch of stuff? Also see if you can find files named "libboost_XYZ-mt.dll" inside C:/MinGW/install/lib.

Both the lot of stuff as well as all the libboost_bla-mt.dll files exist in the described locations.

Nimbal wrote:: Can you paste the output of the setup script to Pastebin? You can use the Powershell ISE (which should already be installed on Windows 7) to get a console that remembers more than 20 lines.

Is that available somewhere after closing Powershell or do I have to let the script run again to get its output "back"?

Nimbal wrote:: Is there anything inside the directory it mentions? Maybe try initializing and updating the googletest submodule once more.

I tried updating the submodules for two more times, but the googletest directory remains empty.

Subject: Re: Development troubleshooting Tue Oct 29, 2013 3:37 am

HariboTer wrote:: Both the lot of stuff as well as all the libboost_bla-mt.dll files exist in the described locations.

Interesting. I didn't expect that (queue X-Files music). Alright, more diagnostic. Open up the CMake GUI and check the box saying "Show advanced variables" (or similar). In the table below that, there should be quite a few entries beginning with "Boost_". I'm particularly interested in the values for "Boost_INCLUDE_DIR", "Boost_LIBRARY_DIRS" and "Boost_SYSTEM_LIBRARY".

Now, delete everything in your build directory, then go through the steps with CMake again. Is it the same result?

HariboTer wrote:: Is that available somewhere after closing Powershell or do I have to let the script run again to get its output "back"?

Unfortunately, you'll have to run it again (in the ISE, not with the normal DOS window that only saves that last 50 lines or so). Note to self: Figure out how to add logging to the PowerShell scripts.

HariboTer wrote:: I tried updating the submodules for two more times, but the googletest directory remains empty.

Without an error message, I really can't help you there. I only use TortoiseGit (I assume that's what you're using) occasionally, so I'm not sure what may have gone wrong. All I can say is that the submodule hasn't been cloned properly. As a last resort, try cloning the whole project again in a fresh directory.

Subject: Re: Development troubleshooting Tue Oct 29, 2013 4:19 am

I will add, that i tried resolving (the same error as above) by copying the entire mingw folder (where the script put all the stuff) to my laptop and running cmake with the copied folders toolchain, which didn't help, so i assume that rules out the PS script.

Subject: Re: Development troubleshooting Tue Oct 29, 2013 4:26 am

Did you copy it to the exact same path? If not, you would also need to update the toolchain file. It might also be an issue with user permissions.

And just to clarify, you tried running the setup script on the laptop and got the errors HariboTer is describing. Then you copied the working mingw environment from your desktop over to the laptop and got the exact same error? Did you check that with a fresh, empty build directory?

Subject: Re: Development troubleshooting Tue Oct 29, 2013 7:18 am

My case in name of the folder might have been different, i can try again, although i imagine it would give different errors if that was the issue.

Nimbal wrote:: And just to clarify, you tried running the setup script on the laptop and got the errors HariboTer is describing. Then you copied the working mingw environment from your desktop over to the laptop and got the exact same error? Did you check that with a fresh, empty build directory?

Yep, and i just tried again: I re-copied MinGW script output folder with the exact same path as my desktop (C:\MinGW), i deleted cmakes cache and deleted everything in the build directory.

My Cmake output is:

Code:: The C compiler identification is GNU 4.7.3
The CXX compiler identification is GNU 4.7.3
Check for working C compiler: C:/MinGW/bin/gcc.exe
Check for working C compiler: C:/MinGW/bin/gcc.exe -- works
Detecting C compiler ABI info
Detecting C compiler ABI info - done
Check for working CXX compiler: C:/MinGW/bin/g++.exe
Check for working CXX compiler: C:/MinGW/bin/g++.exe -- works
Detecting CXX compiler ABI info
Detecting CXX compiler ABI info - done
Looking for OGRE...
OGRE_PREFIX_WATCH changed.
Could NOT find PkgConfig (missing: PKG_CONFIG_EXECUTABLE)
Found Ogre Byatis (1.8.1)
Found OGRE: optimized;C:/MinGW/OgreSDK/lib/release/libOgreMain.dll.a;debug;C:/MinGW/OgreSDK/lib/debug/libOgreMain_d.dll.a
Looking for OGRE_Paging...
Found OGRE_Paging: optimized;C:/MinGW/OgreSDK/lib/release/libOgrePaging.dll.a;debug;C:/MinGW/OgreSDK/lib/debug/libOgrePaging_d.dll.a
Looking for OGRE_Terrain...
Found OGRE_Terrain: optimized;C:/MinGW/OgreSDK/lib/release/libOgreTerrain.dll.a;debug;C:/MinGW/OgreSDK/lib/debug/libOgreTerrain_d.dll.a
Looking for OGRE_Property...
Found OGRE_Property: optimized;C:/MinGW/OgreSDK/lib/release/libOgreProperty.dll.a;debug;C:/MinGW/OgreSDK/lib/debug/libOgreProperty_d.dll.a
Looking for OGRE_RTShaderSystem...
Found OGRE_RTShaderSystem: optimized;C:/MinGW/OgreSDK/lib/release/libOgreRTShaderSystem.dll.a;debug;C:/MinGW/OgreSDK/lib/debug/libOgreRTShaderSystem_d.dll.a
OIS_PREFIX_PATH changed.
Could NOT find PkgConfig (missing: PKG_CONFIG_EXECUTABLE)
CMake Error at cmake_modules/FindBoost.cmake:1192 (message):
  Unable to find the requested Boost libraries.

  Unable to find the Boost header files. Please set BOOST_ROOT to the root
  directory containing Boost or BOOST_INCLUDEDIR to the directory containing
  Boost's headers.
Call Stack (most recent call first):
  CMakeLists.txt:88 (find_package)

Found PythonInterp: D:/Python33/python.exe (found version "3.3.2")
Looking for include file pthread.h
Looking for include file pthread.h - found
Looking for pthread_create
Looking for pthread_create - not found
Looking for pthread_create in pthreads
Looking for pthread_create in pthreads - not found
Looking for pthread_create in pthread
Looking for pthread_create in pthread - found
Found Threads: TRUE
CMake Error at D:/Program Files (x86)/CMake 2.8/share/cmake-2.8/Modules/FindPackageHandleStandardArgs.cmake:108 (message):
  Could NOT find Bullet (missing: BULLET_DYNAMICS_LIBRARY
  BULLET_COLLISION_LIBRARY BULLET_MATH_LIBRARY BULLET_SOFTBODY_LIBRARY)
Call Stack (most recent call first):
  D:/Program Files (x86)/CMake 2.8/share/cmake-2.8/Modules/FindPackageHandleStandardArgs.cmake:315 (_FPHSA_FAILURE_MESSAGE)
  cmake_modules/FindBullet.cmake:70 (FIND_PACKAGE_HANDLE_STANDARD_ARGS)
  CMakeLists.txt:107 (find_package)

Configuring incomplete, errors occurred!
See also "C:/Users/jacob/Documents/GIT/Thrive/build/CMakeFiles/CMakeOutput.log".
See also "C:/Users/jacob/Documents/GIT/Thrive/build/CMakeFiles/CMakeError.log".

I guess it's not the exact same error, but quite close. I also tried re-running cmake on my desktop to a new build directory (just to make sure it was still working) and it did work.

On an unrelated note, a linux "guru" friend of mine managed to build thrives yesterday (help from me made up for the lack of a readme, submodules etc) Althought he had a minor problems. The libraries in the build/dist/bin/plugins folder, the 6 .a files in there were missing a trailing '_d' that he had to add manually (make was complaining that they didn't exist). Just a minor issue you might want to look at or write to the readme.
He managed to build and run it just fine though! (His collision grids around objects, in-game, were way fancier than mine, different version of bullet/ogre perhaps?)
My linux guru friend is here now, so if you're quick to reply he can give you more details.

EDIT: Got more details of the linux error.

Subject: Re: Development troubleshooting Tue Oct 29, 2013 7:47 am

Nimbal wrote:: Open up the CMake GUI and check the box saying "Show advanced variables" (or similar). In the table below that, there should be quite a few entries beginning with "Boost_". I'm particularly interested in the values for "Boost_INCLUDE_DIR", "Boost_LIBRARY_DIRS" and "Boost_SYSTEM_LIBRARY".

For the first one the value is "Boost_INCLUDE_DIR-NOTFOUND", for the other two I can't find exactly those value mappings, only "Boost_DIR" ("Boost_DIR-NOTFOUND") and Boost_SYSTEM_LIBRARY_[DEBUG / RELEASE] ("Boost_SYSTEM_LIBRARY_DEBUG-NOTFOUND" / "Boost_SYSTEM_LIBRARY_RELEASE-NOTFOUND").

Nimbal wrote:

HariboTer wrote:: I tried updating the submodules for two more times, but the googletest directory remains empty.

Without an error message, I really can't help you there. I only use TortoiseGit (I assume that's what you're using) occasionally, so I'm not sure what may have gone wrong. All I can say is that the submodule hasn't been cloned properly. As a last resort, try cloning the whole project again in a fresh directory.

I'm sorry to disrupt the order, but I just ran the submodule update again and it finally generated something. As I didn't do anything inbetween other than turning my PC off yesterday and booting it today, I have no single clue why it might have worked now xD Running CMake again gives me similar (if not the same) error results though.

CMake output:

Code:: The C compiler identification is GNU 4.7.3
The CXX compiler identification is GNU 4.7.3
Check for working C compiler: C:/MinGW/bin/gcc.exe
Check for working C compiler: C:/MinGW/bin/gcc.exe -- works
Detecting C compiler ABI info
Detecting C compiler ABI info - done
Check for working CXX compiler: C:/MinGW/bin/g++.exe
Check for working CXX compiler: C:/MinGW/bin/g++.exe -- works
Detecting CXX compiler ABI info
Detecting CXX compiler ABI info - done
Looking for OGRE...
OGRE_PREFIX_WATCH changed.
Could NOT find PkgConfig (missing: PKG_CONFIG_EXECUTABLE)
Found Ogre Byatis (1.8.1)
Found OGRE: optimized;C:/MinGW/OgreSDK/lib/release/libOgreMain.dll.a;debug;C:/MinGW/OgreSDK/lib/debug/libOgreMain_d.dll.a
Looking for OGRE_Paging...
Found OGRE_Paging: optimized;C:/MinGW/OgreSDK/lib/release/libOgrePaging.dll.a;debug;C:/MinGW/OgreSDK/lib/debug/libOgrePaging_d.dll.a
Looking for OGRE_Terrain...
Found OGRE_Terrain: optimized;C:/MinGW/OgreSDK/lib/release/libOgreTerrain.dll.a;debug;C:/MinGW/OgreSDK/lib/debug/libOgreTerrain_d.dll.a
Looking for OGRE_Property...
Found OGRE_Property: optimized;C:/MinGW/OgreSDK/lib/release/libOgreProperty.dll.a;debug;C:/MinGW/OgreSDK/lib/debug/libOgreProperty_d.dll.a
Looking for OGRE_RTShaderSystem...
Found OGRE_RTShaderSystem: optimized;C:/MinGW/OgreSDK/lib/release/libOgreRTShaderSystem.dll.a;debug;C:/MinGW/OgreSDK/lib/debug/libOgreRTShaderSystem_d.dll.a
OIS_PREFIX_PATH changed.
Could NOT find PkgConfig (missing: PKG_CONFIG_EXECUTABLE)
CMake Error at cmake_modules/FindBoost.cmake:1192 (message):
Unable to find the requested Boost libraries.

Unable to find the Boost header files. Please set BOOST_ROOT to the root
directory containing Boost or BOOST_INCLUDEDIR to the directory containing
Boost's headers.
Call Stack (most recent call first):
CMakeLists.txt:88 (find_package)

Could NOT find PythonInterp (missing: PYTHON_EXECUTABLE)
Looking for include file pthread.h
Looking for include file pthread.h - found
Looking for pthread_create
Looking for pthread_create - not found
Looking for pthread_create in pthreads
Looking for pthread_create in pthreads - not found
Looking for pthread_create in pthread
Looking for pthread_create in pthread - found
Found Threads: TRUE
CMake Error at C:/Program Files (x86)/CMake 2.8/share/cmake-2.8/Modules/FindPackageHandleStandardArgs.cmake:108 (message):
Could NOT find Bullet (missing: BULLET_DYNAMICS_LIBRARY
BULLET_COLLISION_LIBRARY BULLET_MATH_LIBRARY BULLET_SOFTBODY_LIBRARY)
Call Stack (most recent call first):
C:/Program Files (x86)/CMake 2.8/share/cmake-2.8/Modules/FindPackageHandleStandardArgs.cmake:315 (_FPHSA_FAILURE_MESSAGE)
cmake_modules/FindBullet.cmake:70 (FIND_PACKAGE_HANDLE_STANDARD_ARGS)
CMakeLists.txt:107 (find_package)

Configuring incomplete, errors occurred!
See also "C:/Filestuff/C++/Thrive_builds/CMakeFiles/CMakeOutput.log".
See also "C:/Filestuff/C++/Thrive_builds/CMakeFiles/CMakeError.log".

Nimbal wrote:: Now, delete everything in your build directory, then go through the steps with CMake again. Is it the same result?

Yes.

Nimbal wrote:: Unfortunately, you'll have to run it again (in the ISE, not with the normal DOS window that only saves that last 50 lines or so). Note to self: Figure out how to add logging to the PowerShell scripts.

Ok, after running in with the ISE and being informed by Pasebin that the paste exceeds the limit of 500 KB, seeing that a spoiler makes this post too long, not being able to attach it as txt-file - here is a mediafire link http://www.mediafire.com/view/hbvg1vttpe3wysw/script_output.txt ^^

Subject: Re: Development troubleshooting Tue Oct 29, 2013 8:02 am

crovea wrote:: I re-copied MinGW script output folder with the exact same path as my desktop (C:\MinGW), i deleted cmakes cache and deleted everything in the build directory.

Thanks for testing that. I'm honestly a little stumped here, I hope I can reproduce this somehow when I'm back home. By the way, which CMake versions are you using (both Desktop and Laptop)?

crovea wrote:: The libraries generated doing a step, im not sure which one, was missing a trailing '_d' that he had to add manually

Those were probably the Ogre libraries. I'm a little surprised that simply renaming them worked. The "_d" suffix indicates that they are debug libraries. The "proper" solution would have been to recompile Ogre as a debug build, or compile Thrive as a release build.

HariboTer wrote:: I just ran the submodule update again and it finally generated something

Hm, maybe the remote git repository was unreachable earlier (although unlikely, GitHub is pretty reliable). Anyway, do you still see the error about the missing CMakeLists.txt in the googletest directory? The other errors are unrelated to the missing submodule, but that one should definitely be gone now.

HariboTer wrote:: here is a mediafire link

Thanks. Nothing overly suspicious in there, apart from an error message about OpenCL missing. Doesn't look serious, but I'll check whether I get this too.

In the meantime, you could try and add a new entry to the CMake configuration. Name it "Boost_ROOT", make it a string value and set it to "C:/MinGW/install".

Subject: Re: Development troubleshooting Tue Oct 29, 2013 8:11 am

Nimbal wrote:: Anyway, do you still see the error about the missing CMakeLists.txt in the googletest directory? The other errors are unrelated to the missing submodule, but that one should definitely be gone now.

As far as I can tell, I can not find that error any more.

Nimbal wrote:: In the meantime, you could try and add a new entry to the CMake configuration. Name it "Boost_ROOT", make it a string value and set it to "C:/MinGW/install".

Configuring with that produced the following

error log:

and after "fixing" the spelling:

error log nr. 2:

Subject: Re: Development troubleshooting Tue Oct 29, 2013 8:16 am

They check for capitalization? Oh well, seems to work. Alright, do the same for BULLET_ROOT now, same path.

Subject: Re: Development troubleshooting Tue Oct 29, 2013 8:18 am

Code:: Looking for OGRE...
Could NOT find PkgConfig (missing: PKG_CONFIG_EXECUTABLE)
Found Ogre Byatis (1.8.1)
Found OGRE: optimized;C:/MinGW/OgreSDK/lib/release/libOgreMain.dll.a;debug;C:/MinGW/OgreSDK/lib/debug/libOgreMain_d.dll.a
Looking for OGRE_Paging...
Found OGRE_Paging: optimized;C:/MinGW/OgreSDK/lib/release/libOgrePaging.dll.a;debug;C:/MinGW/OgreSDK/lib/debug/libOgrePaging_d.dll.a
Looking for OGRE_Terrain...
Found OGRE_Terrain: optimized;C:/MinGW/OgreSDK/lib/release/libOgreTerrain.dll.a;debug;C:/MinGW/OgreSDK/lib/debug/libOgreTerrain_d.dll.a
Looking for OGRE_Property...
Found OGRE_Property: optimized;C:/MinGW/OgreSDK/lib/release/libOgreProperty.dll.a;debug;C:/MinGW/OgreSDK/lib/debug/libOgreProperty_d.dll.a
Looking for OGRE_RTShaderSystem...
Found OGRE_RTShaderSystem: optimized;C:/MinGW/OgreSDK/lib/release/libOgreRTShaderSystem.dll.a;debug;C:/MinGW/OgreSDK/lib/debug/libOgreRTShaderSystem_d.dll.a
Could NOT find PkgConfig (missing: PKG_CONFIG_EXECUTABLE)
Could NOT find PythonInterp (missing: PYTHON_EXECUTABLE)
Could NOT find Doxygen (missing: DOXYGEN_EXECUTABLE)
Configuring done

Seems to have worked
Now back to the next step in the readme^^

Subject: Re: Development troubleshooting Tue Oct 29, 2013 8:19 am

Great to hear! I'll add those two to the toolchain file so future vict... err... contributors won't face the same problem.

Subject: Re: Development troubleshooting Tue Oct 29, 2013 8:30 am

Alright, generatic from CMake worked, opening and building the project with Code::Blocks worked too (0 errors, 1 warning). Running Thrive.exe didn't
"The application can not be started, because libgcc_s_sjlj-1.dll is missing on the computer. Install the program again to fix the problem" (loosely translated from german^^)
What now?

Subject: Re: Development troubleshooting Tue Oct 29, 2013 8:36 am

In the dropdown near the build button, select the "install" target and build it. Then navigate to the directory "your_build_dir/dist/bin" and start Thrive from there.

Explanation: Starting Thrive from within Code::Blocks runs the executable inside the build directory. Unfortunately, the files that the application needs to run (scripts, textures, models and libraries) must be in very specific paths relative to the executable. The DLLs, for example, must be in the same directory as the executable. The "install" target creates the expected directory structure and copies all required files to the right place. It also rebuilds the executable if you changed some source code, so you can leave the build target at "install".

After some research just now, I may have gotten an idea how to make this a bit easier. No promises, though.

Edit: Slightly better explanation.

Subject: Re: Development troubleshooting Tue Oct 29, 2013 8:40 am

Good to hear things are working with cmake now, ill see if it worked for me aswell in a few hours, busy atm.

HariboTer run the exe inside dist/bin instead of the one at root in build. Also i recommend you use the install build target (perhaps nimbal clarify the build targets and their purpose)

EDIT: I see nimbal commented the same as me. Question: Can we run a different target that doesn't re-copy all the stuff?

» I would like to help development.
» Microbe Stage Development
» Hello development team
» Microbe Stage Progress Report
» Two Questions Concerning Thrive's Development