Closed GoogleCodeExporter closed 9 years ago
From Tyler's email on 2009/02/10:
Good day,
I had not tried a Windows console build of p14p in a while, and I just
re-installed Visual C++ 2008 Express with SP1 on a fresh machine, so I
thought I would see where things stand. Here are some comments.
Note that I updated the platform/windows/pmfeatures.h to align with
platform/desktop/pmfeatures.h, assuming that this is the most up-to-
date and most similar to what I want for the Windows build.
- Error: src/vm/strobj.c, line 252: I did not know that GCC could do
this, but the MS compiler certainly cannot handle a compile-time array
declaration with values that are only available at tun-time.
- Warning: src/vm/img.c, line 116: the PmString_t.length field is
defined as uint16_t and is passed to a function img_findInPAth which
expects a uint8_t. This generates a warning 'possible loss of data'
- Warning: pm.h, line 96: C_ASSERT is also defined in the MS Windows
includes, so we get a 'macro redefinition' warning.
Original comment by dwhall...@gmail.com
on 26 Feb 2010 at 1:56
- Using windows_08_a.zip from python-on-a-chip google group "Files" section.
Unzipped
it in the platform directory.
- Updated platform/windows/README to reflect changes in src/tools/ipm.py
- Updated pmfeatures.h
(updates on local trunk, waiting on other outstanding issues before mainlining)
Original comment by dwhall...@gmail.com
on 27 Feb 2010 at 3:45
Changing Milestone-r10 to Milestone-r09
Original comment by dwhall...@gmail.com
on 7 Mar 2010 at 6:26
WARNING: THIS CODE WAS NOT TESTED BEFORE COMMITTING TO TRUNK! Please help me
test it
by trying to build for windows and discussing any trouble on the maillist; if
we find
bugs, we'll make issues and fix them.
Mainlined directly, see r446
Original comment by dwhall...@gmail.com
on 11 Mar 2010 at 2:57
Original comment by dwhall...@gmail.com
on 11 Mar 2010 at 2:57
Changed r09 to R09
Original comment by dwhall...@gmail.com
on 12 Mar 2010 at 8:22
Original comment by dwhall...@gmail.com
on 13 Mar 2010 at 1:30
Original issue reported on code.google.com by
dwhall...@gmail.com
on 25 Feb 2010 at 10:19