Eagle import - Invalid hexadecimal number in input/source
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
KiCad |
Fix Released
|
Medium
|
Maciej Suminski |
Bug Description
Importing an eagle file on OSX generates hex numbers inside the file that are not accepted by the windows build of KiCad. Doing the reverse (importing in windows and opening on OSX) is no problem as the hex numbers are smaller in the windows import.
Screenshots and more details can be found here:
https:/
It looks like this could be a 32bit vs 64bit problem.
-> OSX platform:
Application: kicad
Version: (5.0.0-
Libraries:
wxWidgets 3.0.4
libcurl/7.54.0 SecureTransport zlib/1.2.8
Platform: Mac OS X (Darwin 16.7.0 x86_64), 64 bit, Little endian, wxMac
Build Info:
wxWidgets: 3.0.4 (UTF-8,STL containers,
Boost: 1.61.0
Curl: 7.43.0
Compiler: Clang 7.3.0 with C++ ABI 1002
Build settings:
USE_
USE_
KICAD_
KICAD_
KICAD_
KICAD_
BUILD_
KICAD_
KICAD_SPICE=ON
-> Windows platform:
Application: kicad
Version: (5.0.0-
Libraries:
wxWidgets 3.0.3
libcurl/7.54.1 OpenSSL/1.0.2l zlib/1.2.11 libssh2/1.8.0 nghttp2/1.23.1 librtmp/2.3
Platform: Windows 8 (build 9200), 64-bit edition, 64 bit, Little endian, wxMSW
Build Info:
wxWidgets: 3.0.3 (wchar_t,wx containers,
Boost: 1.60.0
Curl: 7.54.1
Compiler: GCC 7.1.0 with C++ ABI 1011
Build settings:
USE_
USE_
KICAD_
KICAD_
KICAD_
KICAD_
BUILD_
KICAD_
KICAD_SPICE=ON
Changed in kicad: | |
importance: | Undecided → Medium |
assignee: | nobody → Maciej Suminski (orsonmmz) |
status: | New → In Progress |
Changed in kicad: | |
milestone: | none → 5.0.0-rc2 |
Changed in kicad: | |
status: | Fix Committed → Fix Released |
It looks like the timestamp generated in osx is 64 bit, while the one from windows is 32 bit.