Python error while compiling about ergodox-firmware HOT 6 CLOSED

Here is the offending code:

def parse_mapfile(map_file_path):
        """Parse the '.map' file"""

        def parse_keyboard_function(f, line):
                """Parse keyboard-functions in the '.map' file"""

                search = re.search(r'(0x\S+)\s+(0x\S+)', next(f))
                position = int( search.group(1), 16 )
                length = int( search.group(2), 16 )

                search = re.search(r'0x\S+\s+(\S+)', next(f))
                name = search.group(1)

from ergodox-firmware.

Did you miss this?

The toplevel build process (for generating the ui-info file and such) isn't really intended to be portable. ... Navigate to the src directory (not the toplevel directory) in a terminal, and type make.

from ergodox-firmware.

I did see that but it wasn't clear to me 'portable from what', or what environment you use, so I could try and match it.

Do you mind if I update the readme to clarify for other new users? What environment are you compiling on, I may have missed it...

from ergodox-firmware.

I'm on OS X, with the AVR toolchain from macports. The script was current with my environment a year ago or so. See issue #19 if you're curious for more specifics.

Really, unless you're trying to generate the svg/html layout picture, there's really no reason to compile from the top-level. Still, this question comes up often enough that I've decided comment out the offending code. It isn't really needed any more anyways... Please see the latest commit on master -- if that doesn't work, let me know :)

Is there any reason, by the way, that you're using the master branch? For most people the partial-rewrite branch would be preferable, even if it is a dev branch, with all the caveats that implies (except that it's pretty stable).

from ergodox-firmware.

Hi, I created #47 to address some of the small changes I found. Thanks for commenting out the .py problem as well, I'll check that out.

I'm using a Mac with the AVR toolchain from homebrew, I'm surprised they aren't compatible. Maybe its just bitrot or different versions of the toolchain?

Regarding the partial-rewrite branch, I did read the documentation in that case :) and the warnings about it being 'mostly stable' scared me away. I'm looking for something stable enough for day-to-day use, if you think it is, I'll give it a shot!

from ergodox-firmware.

I'll check that out when I have time (could be a while... sorry!).

Probably different versions... lol, those tools were never meant to be used the way I was using them. Better ideas for a UI and remapping software surfaced before much came of that old approach, so it's really a non-issue now.

Hehe. Thanks for taking it seriously :) . The partial-rewrite branch is definitely stable enough to use: I've been using it for quite some time without functional modification. When development picks up (at some undetermined point :( ...) it might become a bit less so -- but I'll do my best to always keep it working. I've been contemplating some pretty far reaching changes, so in that sense it's not really stable, since the design of things is subject to change -- but you're always free to not merge unless you feel like it. And I feel like the current state of partial-rewrite, even without good top-level documentation, is easier to work with than the current state of master. Unless you want media keys, or any of the other things that have been done by other people on that branch. :)

from ergodox-firmware.