Hey
I thought that this problem was fixed, but it seems it is not. The
automated builds still have the .la files. Can you remove them, please
?
Adrien suggested to use, with gnu tar : --wildcards --exclude="*.la"
thank you
Vincent Torri
-
Hi,
the below patch fixes the definitions of SYSTEM_BASIC_INFORMATION and
adds a definition of SYSTEM_PAGEFILE_INFORMATION and
SystemPagefileInformation. It also changes the formatting of
SYSTEM_INFORMATION_CLASS to make it a bit more readable. Tested on 32
and 64 bit.
Ok to apply?
Btw., I cou
On Mon, Nov 12, 2012 at 8:01 AM, Václav Šmilauer wrote:
>
>> Common practice is to put the DLL in the $PREFIX/bin directory and to
>> put the import libraries in $PREFIX/lib. Since it is common practice
>> doing otherwise might upset your users.
> What do you mean by import libraries here? DLLs wh
2012/11/12 Václav Šmilauer
>
> > Common practice is to put the DLL in the $PREFIX/bin directory and to
> > put the import libraries in $PREFIX/lib. Since it is common practice
> > doing otherwise might upset your users.
> What do you mean by import libraries here? DLLs which get
> LoadLibraryEx'
> Common practice is to put the DLL in the $PREFIX/bin directory and to
> put the import libraries in $PREFIX/lib. Since it is common practice
> doing otherwise might upset your users.
What do you mean by import libraries here? DLLs which get
LoadLibraryEx'd at runtime and which are not needed f
On Mon, Nov 12, 2012 at 5:58 AM, Václav Šmilauer wrote:
> Hi there,
>
> I would like to ask what the best/recommended practice for installing
> shared libraries under Windows/mingw is. Qt4 for instance installs DLLs
> to both $PREFIX/bin and $PREFIX/lib. I prefer to install to $PREFIX/lib
> and add
> It it possible to split the object file? Just move some functions to
> their own implementation file, and link those together. There might be
> less automagical inlining, but overall difference in performance
> should be negligible, and a single object's size should decrease
> significantly.
2012/11/12 Václav Šmilauer
>
> > I am using your toolchains (thanks for them :-) ), the 64bit flavor. Are
> > those messages indicative of files being too big, or is it rather large
> > number of sections (lots of templates?) the culprit?
> >
> >
> c:/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/4.7
> I am using your toolchains (thanks for them :-) ), the 64bit flavor. Are
> those messages indicative of files being too big, or is it rather large
> number of sections (lots of templates?) the culprit?
>
> c:/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/4.7.2/../../../../x86_64-w64-mingw32/bin/as.e
Hi there,
I would like to ask what the best/recommended practice for installing
shared libraries under Windows/mingw is. Qt4 for instance installs DLLs
to both $PREFIX/bin and $PREFIX/lib. I prefer to install to $PREFIX/lib
and add it to $PATH (in addition to $PREFIX/bin), but I wonder if there
On 11/12/2012 16:22, Xiaofan Chen wrote:
> On Mon, Nov 12, 2012 at 3:55 PM, Pau Garcia i Quiles
> wrote:
>> As for your concerns about CMake being available or not: it's
>> available from all Linux and BSD variants I know because more and more
>> projects are moving to CMake because more and more
On Mon, Nov 12, 2012 at 3:55 PM, Pau Garcia i Quiles
wrote:
> As for your concerns about CMake being available or not: it's
> available from all Linux and BSD variants I know because more and more
> projects are moving to CMake because more and more projects are
> concerned about cross-platform, i
12 matches
Mail list logo
