[C++ MinGW32] compilazione wxwidgtes 2.8.5 e codeblocks come fare?

[norih43]

Ho scaricato le wxwidgets 2.8.5 e volevo compilarle con mingw32-gcc-3.4.4 a corredo di codeblocks (nella cartella bin per intederci).... per far questo ho dato il comando:

mingw32-make -f makefile.gcc UNICODE=1 SHARED=0 BUILD=release MONOLITHIC=0

come indicato su il libro wxwidtges..etc...
Ma i risultati sono diversi da quelli sperati, non trovo nè la directory \gcc_dll e forse neanche le librerie statiche..
Inoltre ho provato a creare un progetto con codeblocks impostando la variable con la directory delle wx ma dopo un po che macina mi da diverse undefine reference... Cosa devo fare? dove sbaglio?

Purtroppo ho installato da poco codeblocks, perchè ho sempre usato wxdevcpp che aveva le widgets installate di default, per cui non mi sono mai posto il problema!!:muro: :muro:

[cionci]

Ma hai installato una nightly build di code::block ? La versione RC2 non è più aggiornata da anni.

[norih43]

Si,ho installat la 1.0rc2.... ma nn penso che dipenda da questo. Secondo quanto ho letto, la compilazione doveva produrre delle dll, che io non trovo. hai compilato mai questa lib?

[cionci]

Sì, ma su Visual C++. In ogni caso ti dovrebbe produrre dei .lib (o meglio dei .a per MingW32) se le compili nella versione statica (SHARED=0).

[kk3z]

se fai shared=0 non ti compila le dll ma le librerie statiche.

Oltre allo shared=1 ti consiglio di:
1) usare MONOLITHIC=1
2) aggiornare la versione di code::blocks (scaricala qui (http://download.berlios.de/codeblocks/CB_20071104_rev4596_win32.7z) e qui (http://prdownload.berlios.de/codeblocks/wxmsw28u_gcc_cb_wx286.7z) trovi la dll necessaria)
3) aggiornare la versione di wxWidgets (c'è la 2.8.6)

[norih43]

ma a cosa servono le parole:
SHARED UNICODE BUILD MONOLITHIC
sapete dove trovo una reference, possibilmente veloce?
e se le ometto che succede?

[kk3z]

nel pacchetto msw c'è un file chiamato INSTALLqualcosa.txt con questa sezione:
Basic options
----------------------------------------------------------------

BUILD=release
Builds release version of the library. It differs from default 'debug'
in lack of appended 'd' in name of library, does not define __WXDEBUG__
and not include debug information compiled into object files and the
executable.

SHARED=1
Build shared libraries (DLLs). By default, DLLs are not built
(SHARED=0).

UNICODE=1
To build Unicode versions of the libraries, add UNICODE=1 to make invocation
(default is UNICODE=0). If you want to be able to use Unicode version on
Windows9x, you will need to set MSLU=1 as well.

This option affect name of the library ('u' is appended) and the directory
where the library and setup.h are store (ditto).

WXUNIV=1
Build wxUniversal instead of native wxMSW (see
http://www.wxwidgets.org/wxuniv.htm for more information).

Advanced options
----------------------------------------------------------------

MONOLITHIC=1
Starting with version 2.5.1, wxWidgets has the ability to be built as
several smaller libraries instead of single big one as used to be the case
in 2.4 and older versions. This is called "multilib build" and is the
default behaviour of makefiles. You can still build single library
("monolithic build") by setting MONOLITHIC variable to 1.

USE_GUI=0
Disable building GUI parts of the library, build only wxBase components used
by console applications. Note that if you leave USE_GUI=1 then both wxBase
and GUI libraries are built. If you are building monolithic library, then
you should set wxUSE_GUI to 1 in setup.h.

USE_OPENGL=1
Build wxmsw28_gl.lib library with OpenGL integration class wxGLCanvas.
You must also modify your setup.h to #define wxUSE_GLCANVAS 1. Note that
OpenGL library is always built as additional library, even in monolithic
build!

USE_ODBC=1
Build two additional libraries in multilib mode, one with database
classes and one with wxGrid database support. You must
#define wxUSE_ODBC 1 in setup.h

USE_HTML=0
Do not build wxHTML library. If MONOLITHIC=1, then you must also
#define wxUSE_HTML 1 in setup.h.

USE_XRC=0
Do not build XRC resources library. If MONOLITHIC=1, then you must also
#define wxUSE_HTML 1 in setup.h.

RUNTIME_LIBS=static
Links static version of C and C++ runtime libraries into the executable, so
that the program does not depend on DLLs provided with the compiler (e.g.
Visual C++'s msvcrt.dll or Borland's cc3250mt.dll).
Caution: Do not use static runtime libraries when building DLL (SHARED=1)!

MSLU=1
Enables MSLU (Microsoft Layer for Unicode). This setting makes sense only if
used together with UNICODE=1. If you want to be able to use Unicode version
on Windows9x, you will need MSLU (Microsoft Layer for Unicode) runtime DLL
and import lib. The former can be downloaded from Microsoft, the latter is
part of the latest Platform SDK from Microsoft (see msdn.microsoft.com for
details). An alternative implementation of import library can be downloaded
from http://libunicows.sourceforge.net - unlike the official one, this one
works with other compilers and does not require 300+ MB Platform SDK update.

DEBUG_FLAG=0
DEBUG_FLAG=1
If set to 1, define __WXDEBUG__ symbol, append 'd' to library name and do
sanity checks at runtime. If set to 0, don't do it. By default, this is
governed by BUILD option (if 'debug', DEBUG_FLAG=1, if 'release' it is 0),
but it is sometimes desirable to modify default behaviour and e.g. define
__WXDEBUG__ even in release builds.

DEBUG_INFO=0
DEBUG_INFO=1
Same as DEBUG_FLAG in behaviour, this option affects whether debugging
information is included in the executable or not.

VENDOR=<your company name>
Set this to a short string identifying your company if you are planning to
distribute wxWidgets DLLs with your application. Default value is 'custom'.
This string is included as part of DLL name. wxWidgets DLLs contain compiler
name, version information and vendor name in them. For example
wxmsw283_core_bcc_custom.dll is one of DLLs build using Borland C++ with
default settings. If you set VENDOR=mycorp, the name will change to
wxmsw283_core_bcc_mycorp.dll.

CFG=<configuration name>
Sets configuration name so that you can have multiple wxWidgets builds with
different setup.h settings coexisting in same tree. See "Object and library
directories" below for more information.

[kk3z]

Io solitamente lo compilo così:

mingw32-make -f makefile.gcc UNICODE=1 SHARED=1 BUILD=release MONOLITHIC=1 USE_XRC=1

che tra l'altro sono le opzioni per compilare codeblocks

[limpid-sky]

sapete un modo per sapere come sono compilate le wxwidgest in devcpp?
volevo compilarle allo stesso modo per vedere alcune cose e mi chiedevo se c'era un modo.