Development troubleshooting

Subject: Re: Development troubleshooting Tue Oct 08, 2013 5:21 am

Actually i just git-reverted all the ps1 files as my research told me something fishy were indeed going on with the param stuff. This obviously meant that i had no more transcripting, however i took a lot of screenshots during debug and here are two seemingly relevant ones i managed to capture:

imgur.com/CwXqnTO,syCFpHD

Which did seem to fix the param issues.

I'll add the transcript code again, push my changes and give you my github link once it's done.

EDIT: Here github.com/jjonj/Thrive/tree/Fixing-Build
EDIT2: My first sentence didn't make any sence, fixed.
EDIT3: And just to add, the cmake still gives the cannot find ogre error after i reverted my cmakelists (which i edited out in my post above yesterday).

Subject: Re: Development troubleshooting Tue Oct 08, 2013 6:08 am

Thanks. I'll look into it when I'm back home this evening.

Subject: Re: Development troubleshooting Tue Oct 08, 2013 6:26 am

I am the one who thanks. - [Whalter White picture]

Subject: Re: Development troubleshooting Tue Oct 08, 2013 12:54 pm

My PowerShell does not like the transcript commands you inserted. After reading up on them, it seems to me that start-transcript and stop-transcript are not meant to be used for capturing a script's output, but rather creating a protocol of commands used in a live PowerShell session.

To fully capture the output of a script, you could run it inside the PowerShell ISE, which should already be installed if you are using Windows 7 or later.

Edit: Just to be sure, I just ran the setup script on my machine and then built Thrive. Apart from a little error that must have snuck into a commit when I wasn't looking (oops), everything went smoothly. So I'm a bit lost as to what might be going wrong for you.

Subject: Re: Development troubleshooting Tue Oct 08, 2013 1:27 pm

Here's most of the input

pastebin.com/WcfqAC3d

I took the liberty of removing a couple tens of thousands of lines of just "Extracting X" hopefully i didn't remove any errors

EDIT: Thought i removed the transcription code but i can see its still in the log :S
EDIT2: I did remove it... there's no code where its pointing to, could powershell be caching the files? O.o
EDIT3: Ah foundt ISE was just appending output, just ignore the first part about transcript

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

Well just to reiterate the actual error i'm having in cmake:

Code:: The C compiler identification is GNU 4.7.3
The CXX compiler identification is GNU 4.7.3
Check for working C compiler: B:/MinGW/bin/gcc.exe
Check for working C compiler: B:/MinGW/bin/gcc.exe -- works
Detecting C compiler ABI info
Detecting C compiler ABI info - done
Check for working CXX compiler: B:/MinGW/bin/g++.exe
Check for working CXX compiler: B:/MinGW/bin/g++.exe -- works
Detecting CXX compiler ABI info
Detecting CXX compiler ABI info - done
Looking for OGRE...
OGRE_PREFIX_WATCH changed.
Found PkgConfig: D:/Users/Crovea/Downloads/pkg-config/bin/pkg-config.exe (found version "0.26")
checking for module 'OGRE'
  package 'OGRE' not found
Could not locate OGRE
CMake Error at cmake_modules/FindPkgMacros.cmake:112 (message):
  Required library OGRE not found! Install the library (including dev
  packages) and try again. If the library is already installed, set the
  missing variables manually in cmake.
Call Stack (most recent call first):
  cmake_modules/FindOGRE.cmake:219 (findpkg_finish)
  CMakeLists.txt:57 (find_package)

as mentioned in my previous comments, i had it finding ogre with some manual moving things around and editing cmakelists perhaps i should continue with hacking at it like that?

Subject: Re: Development troubleshooting Tue Oct 08, 2013 1:51 pm

You can try, but if my experience with getting that stuff to run properly is any measure, it won't be pleasant.

Before you do that though, could you check what the OGRE_SDK variable in CMake is set to?

Subject: Re: Development troubleshooting Tue Oct 08, 2013 1:59 pm

Something wierd: my B drive installation of mingw (B:/MinGW/OgreSDK.), i discovered right after my last comment. The last 36 hours i've been using my C:/MinGW/

Subject: Re: Development troubleshooting Tue Oct 08, 2013 2:01 pm

Ah, ok. CMake is pretty zealous about caching and it can be hard to get rid of cached values. The surefire way is to just delete the build directory and create a new, empy one. Could you try that and report back?

Subject: Re: Development troubleshooting Tue Oct 08, 2013 2:03 pm

I've been doing that for atleast half my attempts, it doesnt seem to do anything

How does it know where to look for MinGW? it's not in any of the files directly obviously and not in PATH

EDIT: I'm trying to run the ps1 script on the B installation of MinGW again and it's giving me a TON of ogre related compiler warnings it didn't give me before. I guess thats a good sign perhaps?

Subject: Re: Development troubleshooting Tue Oct 08, 2013 2:07 pm

It's in the toolchain file that you give it when you first click "Configure". You do give CMake the toolchain file, do you?

Subject: Re: Development troubleshooting Tue Oct 08, 2013 2:14 pm

Yeah i do give it "a" toolchain file, never really gave much thought to which one, ill look into it

Yep, changing it to my C drive toolchain seem to have fixed it it just gives me this warning that i'm not sure how seriously to take:

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

D:/Users/Documents/git/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 Warning (dev) at CMakeLists.txt:156 (add_subdirectory):
The source directory

D:/Users/Documents/git/Thrive/contrib/luabind

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.

Anyway thank you very much for all the help xD i knew it was bound to be some stupid mistake i made

Subject: Re: Development troubleshooting Tue Oct 08, 2013 2:16 pm

The toolchain file is generated by the setup script, including absolute paths to the installed executables and libraries. So be sure to select the one that resides in the build environment you want to use.

Subject: Re: Development troubleshooting Tue Oct 08, 2013 2:19 pm

As mentioned above cmake actually completed now, but it didn't produce a project file, must be associated with the above warning i presume?

EDIT: no files in the build/src folder was produced at all

Subject: Re: Development troubleshooting Tue Oct 08, 2013 2:22 pm

Oh, right. Simple fix, for once. Our repository uses git submodules to pull in dependencies from external git repositories. Unfortunately, git doesn't automatically clone those submodules when cloning our repository. If you are using TortoiseGit, look for an option like "Submodule Update" or similar. Then rerun CMake.

Also, you might want to pull from the main repository before building because I fixed a syntax error an hour or so ago.

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

Yeah i remembered there was something about those warnings in the readme and managed to remove the warnings effordlessly. ~~HOWEVER still no project file or any files in build/src~~

Also with pull you mean rebase right? i'm not super familiar with the more advanced git features

EDIT: NVM ME!!!! I forgot to generate... lol
EDIT2: And with main repo you mean prototype branch right?

Subject: Re: Development troubleshooting Tue Oct 08, 2013 2:31 pm

The Code::Blocks project file should appear directly in the build directory, not in build/src.

Also, a "git pull" is a "git fetch" (download new commits from a remote repository), followed by a merge to combine those new changes with any you might have committed since your last pull.

A "git rebase" is a special kind of merge (i.e. the second part of a pull) that, instead of applying a bunch of commits from two branches in chronological order, applies first all commits from one branch, then all commits from another branch. This page has some excellent diagrams and explanations if you want to know more.

Edit: Great to hear you got it to work. And yes, I mean you should take your prototype branch and update it so it has the latest changes from the original prototype branch. You'll need to add the main repository as a new remote "main" (or whatever you'd like to call it), then make a pull from "main/prototype".

Subject: Re: Development troubleshooting Tue Oct 08, 2013 2:35 pm

Yeah the missing files were just me forgetting to generate

And i thought i read somewhere on the forums here that we needed to "rebase" from the main repo as we each have our own forked one.
So you're saying i just need to pull from github.com/Revolutionary-Games/Thrive/tree/prototype, ill give it a go

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

So yeah, still having trouble adding the main repo as a remote in git and having it actually work but i'm not going to bother you with that.

I managed to build the project and finally get an executable, but it's complaining about missing gcc library dll (libgcc_s_sjlj-1.dll) when i try to run it. Furthermore in order to actually build it in codeblocks i had to manually add the gcc compilers (it had the right path, but the files it tried to use were prefixed with mingw while the actual compiler exes were just 'g++.exe' etc)

I assume the setup should have included these dll files? (the run tests is complaining about another dll)

EDIT: The dll files are in the C:\MinGW\bin folder, just need to link it somehow. Makes me think cmake didn't configure codeblocks correctly.

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

I think the manual setup for Code::Blocks is normal. To get those dlls all in one place, "build" the target called "install". That will copy all the necessary stuff into the "dist" subdirectory of your build directory.

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!

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