- This topic has 0 replies, 1 voice, and was last updated 1 month, 2 weeks ago by
.
-
Posts
-
(This message was transferred over from our old forum)
Posted August 19, 2015
By Todd DeBoer
[hr]
On 9/17/2010 rjmmusic asked, “Hello, I’m getting started with uEZ running on the LPC2478 dev kit, and I’m using Rowley Crossworks on a Mac. In trying to build the uEZ demo, I’ve noticed that most of the #include paths use backslashes instead of forward slashes. This causes an error on the Mac version, and I assume would also cause the same problem on Linux (also supported by Rowley). I’m changing all of the files now, but I’d like to request that you use the more compatible forward slash paths in future versions so we non-Windows users don’t have to change all the files.Thanks very much for a great product! The developer kit plus uEZ is going to make my life a lot easier.”
[hr]
(Follow up post)Answered:
We have agreed to move to using forward slashes. Not sure if we will catch all of them, but there is more of an effort to change that now.
- You must be logged in to reply to this topic.