In the future (if I recall it correcty) the LCL only uses LMessages and no target shall use Messages (only the win32 interface shall)

Marc

Hi
I have problems with unit MESSAGES
are two unit with the same name
pp\units\rtl\win32
and
lazarus\lcl\nonwin32

WHY they have the same name
in compilation is very hard to discover which one is need and compilations LMESSAGES under WIN32 and FPC1.9 cause curcular error

they are two solutions:
1. rename NONWIN32\MESSAGES to NONWIN32\NMESSAGE

or

2. move all stuff to LMESSAGES with conditional compilation:

{$IFDEF WIN32}
  uses messages;
  LM_DROPFILES     = WM_DROPFILES;
{$ELSE}
  LM_DROPFILES      = $0233;
  WM_DROPFILES     = LM_DROPFILES;
{$ENDIF}

Darek

Because the non-win32 rtl doesn't have this unit.

in compilation is very hard to discover which one is need and compilations LMESSAGES under WIN32 and FPC1.9 cause curcular error

This nonwin32 directory shouldn't be used in the include path for the win32 target. I don't have a problem building the sources. What do you do, what specific error do you get?

Micha.

Ok now I understand

I have to do change my FPC.CFG file with conditional (I use command line compilation)

But I think that use the same name of unit is not very usefull. I read mail from Marc. He planed that no one (form LCL) use Messages, that what for is asking unit.

Darek