Page 1 of 1
Issue-Tracking for UMDK
Posted: Tue Jun 24, 2014 1:31 pm
by MintyTheCat
Hi Prophet,
how would you like us to notify you of any issues with the Sourcecode for UMDK?
I have just patched a slight issue with your paths having checked if the issue was still present in your UMDK's Dev Branch, it was so I shall email you the Patch.
Cheers,
Minty.
Posted: Tue Jun 24, 2014 2:01 pm
by prophet36
It looks like you're using an incorrect branch. If you're a UMDK
user, you should use a specific release; the most recent is 20140524:
Code: Select all
$ cd $HOME
$ mkdir 20140524
$ cd 20140524
$ wget -qO- http://makestuff.eu/bil | tar zxf -
$ cd makestuff/
$ scripts/msget.sh makestuff/hdlmake/20140524
Fetching "makestuff/hdlmake/20140524"...
Uncompressing "makestuff/hdlmake/20140524" into "hdlmake" directory...
Fetching "makestuff/common/20140524"...
Uncompressing "makestuff/common/20140524" into "./common" directory...
$ cd hdlmake/apps/
$ ../bin/hdlmake.py -g makestuff/umdkv2
MakeStuff HDL Builder (C) 2012-2013 Chris McClelland
Fetching https://github.com/makestuff/umdkv2/archive/20140524.tar.gz
Success!
$ cd makestuff/umdkv2/
$ ls
COPYING COPYING.LESSER gdb-bridge hackdump loader logread m68k README scripts templates vhdl
$ grep -E '^ROOT' logread/Makefile
ROOT := $(realpath ../../../../..)
$
Conversely, if you're a UMDK
developer, you should use the dev branch:
Code: Select all
$ cd $HOME
$ mkdir dev
$ cd dev
$ wget -qO- http://makestuff.eu/bil | tar zxf -
$ cd makestuff/
$ scripts/msget.sh makestuff/hdlmake/dev
Fetching "makestuff/hdlmake/dev"...
Uncompressing "makestuff/hdlmake/dev" into "hdlmake" directory...
Fetching "makestuff/common/dev"...
Uncompressing "makestuff/common/dev" into "./common" directory...
$ cd hdlmake/apps/
$ mkdir makestuff
$ cd makestuff/
$ ../../../scripts/msgit.sh makestuff/umdkv2
Cloning into 'umdkv2'...
remote: Reusing existing pack: 1054, done.
remote: Total 1054 (delta 0), reused 0 (delta 0)
Receiving objects: 100% (1054/1054), 368.83 KiB | 382.00 KiB/s, done.
Resolving deltas: 100% (622/622), done.
Checking connectivity... done.
$ cd umdkv2/
$ ls
COPYING COPYING.LESSER gdb-bridge hackdump loader logread m68k README scripts templates vhdl
$ grep -E '^ROOT' logread/Makefile
ROOT := $(realpath ../../../../..)
$
For bug-reporting, GitHub already has a web-based tool for it:
https://github.com/makestuff/umdkv2/issues
Posted: Tue Jun 24, 2014 5:19 pm
by MintyTheCat
I was a naughty boy: I grabbed the tree as a compressed-file directly from the Dev Branch's page instead of cloning correctly.
All is now well and Logread now builds without me having to modify the Makefile's Path - thanks.
Sorry - I saw your link underneath for issue tracking - cheers.
Posted: Tue Jun 24, 2014 5:29 pm
by prophet36
That's actually all the msget.sh script does (whereas the msgit.sh script actually does a git clone). My theory is you actually downloaded the zip for the master branch. In theory the master branch should point at the same commits as the most recent label. In practice, not so much.
Anyway, glad you got it sorted!
Posted: Tue Jun 24, 2014 9:19 pm
by MintyTheCat
Yes, it gave me the Master instead of Dev. I added my Key and then got the Dev - no worries now.