Compiling with biicode: CMake, build process, IDEs and more

biicode knows how source code files connect to each other. With this information, it creates a boilerplate CMake layout to build your project automatically. biicode then detects how sources connect and builds a dependency graph following #includes and implementations generating, for each block, a CMakeLists.txt defining variables to the dependency graph detected.

This translates into a CMakeLists.txt file with just one line by default:

Even though the boilerplate might be enough for some projects, here’s a guide to fully control the building process.

Today, we explain the different options available in biicode once you’ve got your CMakeLists.txt ready.

Compiling with biicode

Continue reading

biicode’s new basics – git remote linking, collaborators and more

We have decided to move out of beta some of our coolest features and allow any user enjoy them. Today we are featuring git remote linking and block collaborators management but we release every two to three weeks so expect new features like these coming every fortnight or so. These functionalities are now available to all biicode users. Enjoy! you can always suggest or upvote the existing features that are ahead in our roadmap here.

Continue reading

New feature: Version Tags

Biicode is not a Version Control System, neither a Source Code Management System. As a dependency manager, biicode makes “some kind” of internal version control to establish dependencies against a specific version of the block.

Our versions are incremental integers starting on 0. Until now,  to know that biicode’s version corresponds to any official version you had to look for it on the block’s description or readme.

Now you can tag a version while publishing. For example, qiangwu/atlstl corresponds to the official “1.9.98” version:

Version tags now available in biicode 2.0

Continue reading

How to upload to biicode. Example 4: Oscpack by Ross Bencina

Updated for biicode 2.0!

As the headline states, this is the fourth example about how to upload libraries to biicode.  If you’ve done this kind of thing before, keep reading, we’ll explain how to upload Oscpack lib. Otherwise, you may be interested on reading first any previous articles of the series:

Continue reading

How to upload to biicode. Example 3: Little CMS by Marti Maria

Updated for biicode 2.0!

Once a library is uploaded to biicode, everyone can reuse it easily!  Let’s see a new example about how to upload to biicode just following a few steps, again, this is another example about how to proceed when your library depends on others. For this matter we’re using the fantastic library Little CMS, a free, open source, CMM engine. It provides fast transforms between ICC profiles.

As you can guess, once we’re done everybody will be able to use this library just by typing #include "martimaria/littlecms/include/lcms2.h"

Continue reading

How to upload to biicode. Example 2: Box2D by Erin Catto

Once you upload to biicodThis example about Box2D shows you how easy to upload to biicode ise a library, everyone can reuse it!  That’s why we explained how to upload to biicode any library just following a few steps, but that example didn’t cover the possibility of a library depending on other libraries, which is quite usual nowadays. So today, we’re going to see with an example how to proceed when your library depends on others. For this matter, we’re using BOX2D, an open source C++ engine to simulate rigid bodies in 2D, it is also used in different video-games like AngryBirds motor engine.

 

Continue reading