Esteban's ChangeLog week of 14 May 2018

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Esteban's ChangeLog week of 14 May 2018

EstebanLM
Hello!

This is my weekly ChangeLog, from 14 May 2018 to 20 May 2018.
You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=14/5/2018&to=20/5/2018

ChangeLog
=========

18 May 2018:
------------

*    The strategy of "just copying" dependencies when they are available has some limitations: we need to copy also dependencies
    we may not want.
   
    I will review these copied libraries (for now: cairo, libssh2 and libgit2) to minimize them. This means I need to review
    versions and maybe compile them myself and put them in the repository.
   
    Still, is not the best approach possible, but is the way I'm finding to move on for now... we'll see how it goes.
   

17 May 2018:
------------

*    I've been working on the Windows 64bit PharoVM compilation.
   
    I needed to hack a lot and take decisions I'm not proud of them, but well... after one week work (and six months
    trying), now I have a 64bit VM with all dependencies compiled.
   
    *But!*... I cannot call it a victory. Dependencies are still not working properly (libgit2 and cairo, at least).
    So now the painful debug phase restarts.
   

16 May 2018:
------------

*    I found an important leak when using OSWindow and SDL2, so I spent some time fixing it (or at least, trying to fix it).
   
    I made two PRs that should fix the problem: [https://github.com/pharo-project/pharo/pull/1368](https://github.com/pharo-project/pharo/pull/1368) and [https://github.com/pharo-project/pharo/pull/1369](https://github.com/pharo-project/pharo/pull/1369)
   

15 May 2018:
------------

*    Spent the day resuming work on win64 VM for Pharo.
   
    I decided stop trying to fight the dependency building hell and start over with a different approach: we will build
    the vm using the available libraries in cygwin64 (when possible) and we will use a separate project to build dependecies
    when we need something cygwin does not provides.
   
    While this approach is far from being perfect, it will allow us to move on.
   
    Anyway... I spent most of the day getting my cygwin environment to work, but I managed to advance a bit anyway.
   

cheers!
Esteban