Category: CMake

If only I had more time...

1/3/2018

As always, when I wrote my last post I was lucky enough to have plenty of time on my hands. Recently however work has been some what manic trying to ensure that our team meets the delivery date for our new feature, which has had a knock on effect with my own projects.

I'm hoping to get back into this CMake work and really revive the JBEngine project but until work lets up I don't think that's going to happen. I'm simply writing this post to try and keep this all at the forefront of my brain. I really don't want my motivation to slip on this again!

Thanks

0 Comments

Back to it... CMake again!

27/1/2018

0 Comments

So I've decided to revive the JBEngine Project. I gave it up a while ago due to lack of motivation when trying to make it cross platform. The main reason for that was the steep learning curve for using CMake and generally having no real milestones for a very long time. The project was in a state of failing compilation for so long that I ended up giving up. So how am I going to be able to motivate myself this time?

Agile, and how it's effected me

So being a Scrum Master at work for the past work or so I've found out how important it is to break tasks down into small manageable goals/stories. In doing this I will be able to keep myself motivated by ticking things off in my task tracking application. There are still going to be a few problems getting started though.

Too many changes!

So during my development almost a year or so ago I had my project in a state where there were many files edited/added such as many CMake files and lots of changes for making the source code cross-platform. Due to my frantic approach at trying to get the project fully working I now have multiple machines with various files edited with no way of knowing which are required, which aren't working correctly and which I need to just get rid of.

Step by Step Plan

I'm going to take things step by step now, just to get the project in a clean state before making any major changes.

I need to figure out which source code changes are really required and get them checked in.
I then need to figure out which of my CMakeLists actually work and get the correct ones checked in.
I will then delete anything else that is not required.

I want 'git status' to tell me that my repo is completely clean before I even consider making any new changes.

That's all for this time,
Thanks

0 Comments

CMake: Compiling Libraries step by step

8/6/2016

0 Comments

So for a while now I've been trying to get the JBEngine cross compiling using CMake. I started this off by creating cross platform versions of the most simple libraries first, Maths and Sound. This was easy because they had very few dependencies and hardly and source code.

I have currently managed to build all the libraries, which are:

Maths
Sound
Networking
Physics
Renderer
Awesomium/GUI
JBEngine

When I have now come to put all this together and compile the Space Invaders executable it has become a nightmare.

There are just too many errors!

Taking a step back

To overcome the sheer amount of issues I have decided to create small test applications with minimal parts of the JBEngine libraries. That way I can narrow down issues, to specific libraries. This is something I had done a while back to check that the Sound library worked. I created an application that loads one sound and plays it on repeat.

Last night I found a tutorial online that uses CMake with glfw, glew and assimp so I managed to get those working nicely. Here is a list of test applications I will make in order:

Window Creation (openGL, glfw, glew)
Window with fullscreen texture (SOIL)
Window with single loaded mesh (assimp)

For now this will do, as I'm not sure exactly which libraries will cause the problems.

I will be separating out the window creation into another library as that seems to make sense. The JBEngine library has become far too bloated, and it will make these test applications easier to create.

Finally I am hoping that by building these test applications, not only will I create a better architecture but I will also keep motivation high. Each little test application can be thought of as a milestone which will be rewarding on completion.

Thanks :)

0 Comments

Development Blog

If only I had more time...

Back to it... CMake again!

Agile, and how it's effected me

Too many changes!

Step by Step Plan

CMake: Compiling Libraries step by step

Taking a step back

Archives

Categories