Re: Strange behaviour with constants, when multiple projects on the same code

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

See View->Other Window->Output (Ctrl + Alt + O) it shows the correct errors for each project.

To tell the truth, I've noticed that you can't rely on information in "Task List" window. Always see what was shown in the "Output Window".


--
Sergey Bogdanov [.NET CF MVP, MCSD]
http://www.sergeybogdanov.com


maluman wrote: 
Hello

I followed Daniel Moth's suggestion on how to target multiple devices, and
something strange happened. I have two projects sharing the same code. They
should differ only in target device and Conditional Compilation Constants.I
have defined WINCE constant in WinCE project and PPC constant in PPC
project.
The problem is that no matter which project I try to build, compiler reads
always the same constants. I reproduced the bug in:
http://maluman.szm.sk/Configurations.zip

Please take a look at defined constants and the beggining of Form1.cs. It
throws a compilation error, depending on defined constant, and in my case it
is always #error 'WINCE defined'. No matter which project I build, no matter
which I choose for startup. Help is much appreciated.
I use VS 2003 7.1.3088.

Regards, m.



.

Relevant Pages

  • Re: Strange behaviour with constants, when multiple projects on the same code
    ... Note that I never mix the two projects that share the code files this way. ... > should differ only in target device and Conditional Compilation ... > have defined WINCE constant in WinCE project and PPC constant in PPC ... No matter which project I build, ...
    (microsoft.public.dotnet.framework.compactframework)
  • Strange behaviour with constants, when multiple projects on the same code
    ... I followed Daniel Moth's suggestion on how to target multiple devices, ... should differ only in target device and Conditional Compilation Constants.I ... have defined WINCE constant in WinCE project and PPC constant in PPC ... The problem is that no matter which project I try to build, ...
    (microsoft.public.dotnet.framework.compactframework)
  • Re: gfortran, g95, and dual-core
    ... either speed of compilation or speed of execution? ... Many, many things matter. ... That's why cache is ... Is this apt to make a big difference (factor of 2 in execution speed) when comparing different Intel-compatible chips in a given price range? ...
    (comp.lang.fortran)
  • Re: Standard C and math library
    ... since the magic words used for compilation and linking are external to the standard, ... In addition, unlike today where it's mostly embedded systems where memory footprint matters at that level of granularity, it once *did* matter -- particularly at the time the convention was adopted. ... I know history in this case:) Anyway the standard C99 is far too young to be affected by math coprocessors and DX/SX distinction. ...
    (comp.lang.c)
  • Re: I was off to the dentist again
    ... stress  will be there no matter if you smoke or not ... wince I was ... smoking nonstop and didn't see one i my 30's. ...
    (alt.support.stop-smoking)