Showing posts with label buildsystems. Show all posts
Showing posts with label buildsystems. Show all posts

Friday, April 8, 2022

Getting rtree (0.9.7) and PyInstaller (3.4) to Work Together

This is a quick note on how to get RTree (0.9.7) and PyInstaller (3.4) to play nicely together, so that if you've got a script using RTree (e.g. for example, a script that calls trimesh.proximity.thickness()) that you need to compile into a .exe so that non-technical users can run it as a standalone binary without setting up a Python dev environment first.

These instructions are based on what worked on the project I'm working on, and are only tested with the versions listed on Windows 10. I haven't actually tested this on Linux, since most of the Linux users of this program are already doing a lot more coding work and will have dev environments set up anyway, that it doesn't matter for them.

Hopefully this helps someone else someday. 


Tuesday, February 7, 2017

Custom MSBuild Loggers for Blender Devs on Windows

Given that it was a long weekend here in NZ, I decided to take a little time off to work on a little "weekend project" I'd been wanting to work on for ages. (BTW, it wasn't the only weekend project I worked on this weekend, but it's the only one that will be of much interest to anyone else :)

Here's an obligatory screenshot showing the results of my work.

 The "cleaned up" Blender build output as a result of my project: blender_msbuild_loggers

Friday, January 22, 2016

CMake + MSVC Frustrations - Solutions Wanted

It's been several weeks since Blender switched over to CMake. While some teething troubles while adapting to a new setup are to be expected, some are more disruptive than others... and it's usually these that are the ones that won't go away!

Having used this new setup for a few weeks, unfortunately, I have to say that there are a few quirks with this new CMake + MSVC setup which are currently very much inferior to my old setup with Scons + Mingw. (Part of the pain has been spared by the fact that I'm working on a pet project in a separate branch that I've purposefully left in a pre-scons-removal state... it will stay that way for as long as possible). If anyone is aware of any solutions to any of these problems, do let me know!


Wednesday, January 6, 2016

Brave New World - Goodbye Scons + Mingw

Today, I finally had to bid farewell to the build system that's been serving me so well for the past 10 years (well, apart from that brief stint where I had to switch over to msvc for a few weeks as the build was broken). Yesterday, the scons build system was finally removed from Blender, leaving just cmake.  *sob*

Wednesday, August 18, 2010

Build Systems in a Rush - A Quick Recipe for SCons (C-Code Compiling)

In general, I like using SCons more than makefiles. Why? Well, the following 3 points are a big drawcard:
  1. It's files are based on Python. So no funking around with yet another ancient/archaic shell language
  2. SCons works nicely (as a 1-step process) on a Windows computer once installed, without needing special shells or whatnot. This practically knocks out CMake (it's a two-step process, which ends up creating makefiles or msvc projectfiles, both of which have their downsides) and standard mingw-makefiles (which I cannot ever seem to get running without using a special msys shell, and/or other arcane invokations) 
  3. Being able to show simplified progress info instead of blurting out compiler commands every time (i.e. "Compiling XYZ" vs "gcc -o afkhaf aghaffoof.c -lfghj -lagfhkja -akfha -Wah -Wajgh -aekfh -laksighf-lajfhjf -alkhaf- lakghaf- -lajigfb -lafgjh..."). Sure, this is doable with makefiles too, but it seems that everytime people do it there, it needs more environment variables to be set. Meanwhile with scons, we can easily turn it on/off with command-line options. No wonder so many people miss and ignore compiler warnings, leading to some very weird bugs in their code (also a factor leading to the issues in a previous post).
Despite this, at times I have resorted to using one of my home-brewed py-scripts to just compile some simple stuff when I've been too lazy to read through the SCons docs to get things done (or when there were some problems which I couldn't fix in time).

Fortunately, this time it didn't happen, so now I think I've finally got a reasonable scons template. The template included here is what I'm using to compile the code for one of my assignments, btw.