[sword-devel] Migrating to the eVC 4.0 Environment
sonwon.1 at gmail.com
Tue Jul 15 19:19:10 MST 2008
Okay, I finally remember how I ported my old application to EVC4; it has
only been 2 years. It isn't pretty. The best way is to create a new
project in EVC4 and migrate the files into the new project. This will
cause the loss of PPC 2002 or older support.
So I did an Internet search and discovered, Microsoft has a kludge to
share code between EVC3 and EVC4. Requires preprocessor settings in the
code. And another unsupported kludge which will allow you to write
WinCE code in EVC4 however the debugger will not work.
Here is the link in case you want to read about it.
If we cannot distribute EVC3 we will loose the ability to write for that
platform eventually. Although perhaps we could debug on the device with
EVC4 rather than an emulator? However there are other problems, read
I think we will need to fork unless we determine we can distribute
EVC3. In that case we can develop in EVC3 for as long as it makes
sense. We will need another svn trunk to support (I hope that is the
correct term.) EVC4 developers and there code will likely not be
compatible with EVC3, ugly.
The only sensible option is to convert all of the devices to Linux and
dump M$. :)
Please give your opinions so we can decide what to do.
I choose God and all that my choice entails in this life even unto death and look forward to the new life that will come.
More information about the sword-devel