Author Topic: why does slickeidt consider WIN32 defined?  (Read 2934 times)

ruian

  • Community Member
  • Posts: 6
  • Hero Points: 0
why does slickeidt consider WIN32 defined?
« on: November 15, 2011, 07:49:11 pm »
Hi, gang:

I work on our own embedded code base.
Recently, tagging starts to bother me, since all the code in #ifndef WIN32 #endif are considered "not active code".
I think Slick Edit is somehow thinking that WIN32 is defined.

Does anyone know how to fix this?
(Those code inside #ifndef WIN32 #endif  are needed for our simulator running on PC. However, they are not even using the same slick edit project file ).

Thanks!
William

hs2

  • Senior Community Member
  • Posts: 2743
  • Hero Points: 288
Re: why does slickeidt consider WIN32 defined?
« Reply #1 on: November 15, 2011, 10:06:52 pm »
It's (pre-)set in 'C/C++ Preprocessing'. You need to 'undef' it and re-tag your workspace (at least).
HS2

ruian

  • Community Member
  • Posts: 6
  • Hero Points: 0
Re: why does slickeidt consider WIN32 defined?
« Reply #2 on: November 15, 2011, 11:04:04 pm »
It's (pre-)set in 'C/C++ Preprocessing'. You need to 'undef' it and re-tag your workspace (at least).
HS2

Hi, HS2:

Thanks for your reply!
Can you let me know how to un-set it?
In workspace properties?

Thank you very much!
William

ruian

  • Community Member
  • Posts: 6
  • Hero Points: 0
Re: why does slickeidt consider WIN32 defined?
« Reply #3 on: November 16, 2011, 02:01:04 am »
Thanks, HS2, I found it.

hs2

  • Senior Community Member
  • Posts: 2743
  • Hero Points: 288
Re: why does slickeidt consider WIN32 defined?
« Reply #4 on: November 16, 2011, 07:49:57 am »
Hi William, I hope it works now as expected.
Beware that this setting is (still) global. This could cause problems when dealing with workspaces dedicated to e.g. an embedded target and (WIN32) host software in parallel.
There is a feature request pending to move this into workspace scope or attach this configuration to the selected compiler.
HS2

ruian

  • Community Member
  • Posts: 6
  • Hero Points: 0
Re: why does slickeidt consider WIN32 defined?
« Reply #5 on: November 16, 2011, 08:06:18 am »
 :) Thanks, HS2!
For now it's okay since I work only on the target code.
But for sure I'll be anticipating that feature, since I use vs for other tasks(PC code) too.

Thanks again!
William