Обсуждение: wxWindows lib name changes

Поиск
Список
Период
Сортировка

wxWindows lib name changes

От
Adam H.Pendleton
Дата:
I just grabbed the CVS tree for wxWindows, and I noticed that the
library naming convention seems to have changed.  Where it used to be
-lwx_macd-2.5 it is now -lwx_macd_core-2.5, etc.  This causes the
autoconf code to fail, since it is looking for "wx_macd-" not
"wx_macd_".  Can anyone else confirm that this change takes place on
other platforms (I realize we don't use the CVS tree for our builds,
but it may be necessary for Mac support).

ahp

Вложения

Re: wxWindows lib name changes

От
Andreas Pflug
Дата:
Adam H.Pendleton wrote:

> I just grabbed the CVS tree for wxWindows, and I noticed that the
> library naming convention seems to have changed.  Where it used to be
> -lwx_macd-2.5 it is now -lwx_macd_core-2.5, etc.  This causes the
> autoconf code to fail, since it is looking for "wx_macd-" not
> "wx_macd_".  Can anyone else confirm that this change takes place on
> other platforms (I realize we don't use the CVS tree for our builds,
> but it may be necessary for Mac support).


There's a new --enable-monolithic switch for wx to compile the lib the
old way.

Regards,
Andreas