Author Topic: Getting a development machine up and running and developing.  (Read 12881 times)


Marsu42

  • Hero Member
  • *****
  • Posts: 1557
  • 66d + flashes
Re: Getting a development machine up and running and developing.
« Reply #1 on: April 04, 2014, 11:24:33 PM »
I recently set up a minimal (70mb packed, ~500mb unpacked) cygwin-x86 for compiling ml and its tools from anywhere w/o fuzz. I see no reason not to share it, but let me know if there's any problem with redistributing this. It's just a copy of cygwin + arm-gcc + exiftool + dcraw with non-en locales and non-eos arm targets removed for convenience. I hope it works for you, I really didn't test it that much in different environments...

https://bitbucket.org/Marsu42/ml-pull/downloads/cw-armgcc-ml.7z

1. unpack (or see below) archive to c:\
2. in c:\cygwin click "Cygwin Terminal" link
3. uncomment the rst2latex.py line in /ml/Makefile.user & adjust other paths there if needed
4. edit /ml/mlmake.sh to match your camera's type and platform directory
5. run /ml/mlget.sh ... your compiled ml will end up in /ml/ml-dist, copy that to card (& run eoscard)
6. from now on only run /ml/mlupdate.sh

To place the cygwin directory somewhere else change the shortcuts/.sh/.bat in the root directory or just create a junction c:\cygwin to the real directory. To update cygwin edit/import the .reg to match your path, run /cygports.sh and select "exp" in the top right for the newest version of the packages. To update gcc-arm get the newest one from launchpad and replace it in /opt.

Let me know if it fails catastrophically :-p so I can make some changes if required.

bischofftep

  • New to the forum
  • *
  • Posts: 17
Re: Getting a development machine up and running and developing.
« Reply #2 on: April 09, 2014, 11:22:05 PM »
Ran into this and others may as well:

If your "make docs" or "make zip" build fails with an error after the words "This is pdfTeX" it may be that your LaTeX install did not include several fonts used by ML's document system.

To fix this on Linux systems, try:
Code: [Select]
apt-get install texlive-fonts-extra
That should install the missing fonts.

The next error I hit was a missing "pylab" module. This comes from:
Code: [Select]
apt-get install python-matplotlib
Douglas E. Bischoff
Audio/Video Production & Scoring

dfort

  • Hero Member
  • *****
  • Posts: 2091
Re: Getting a development machine up and running and developing.
« Reply #3 on: September 25, 2015, 06:53:36 AM »
Cool--a few of the tutorials that I wrote up made it on the list.

Thanks Audionut!

Looks like Compiling Magic Lantern with Cygwin/MinGW-64 is the one that is the most solid and some yet to be merged Windows specific code changes aren't required. The quick start guide allows short attention span users to get going in just a few minutes. There is even a shell script in the discussion that allows users to create their own nightlies almost automatically--though I'm not sure why anyone would want to do that other than because they can
EOSM.202 EOSM.203 EOSM2.103 700D.115 5D3.*

Audionut

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 3444
  • Blunt and to the point
Re: Getting a development machine up and running and developing.
« Reply #4 on: October 17, 2015, 07:10:52 AM »
Thanks for making them.  I've just added your mac one also. 

Feel free to hit me with a stick if I miss any.

FelixJongleur42

  • New to the forum
  • *
  • Posts: 4
Re: Getting a development machine up and running and developing.
« Reply #5 on: December 29, 2016, 01:58:45 AM »
For openSUSE "make docq" was also failing. The missing packages where:
texlive-mathabx
texlive-mnsymbol
texlive-newfile

For detailed error analysis when pdfTeX is failing, check doc/*.log