Hello
I write a test helloworld program.I want to link it against msvcr100.My
enviroment is
os:xp sp3
mingw64 version:ruben build target win32
I compile the program as
gcc -o hello.exe main.cpp -lmsvcr100.
My problem is when I add -lmsvcr100 switch,I run the dependency walker on the
hello.exe,I
On Thu, Jun 20, 2013 at 12:25 PM, Christer Solskogen
wrote:
>
> On 20.06.2013 05:20, Dongsheng Song wrote:
> > On Thu, Jun 20, 2013 at 12:35 AM, Christer Solskogen
> > wrote:
> >> On 19.06.2013 11:37, Dongsheng Song wrote:
> >>> I can build i686-w64-mingw32-gcc and x86_64-w64-mingw32-gcc under
>
On 20.06.2013 05:20, Dongsheng Song wrote:
> On Thu, Jun 20, 2013 at 12:35 AM, Christer Solskogen
> wrote:
>> On 19.06.2013 11:37, Dongsheng Song wrote:
>>> I can build i686-w64-mingw32-gcc and x86_64-w64-mingw32-gcc under
>>> Linux, but when I use this compiler to compile native Windows
>>> compi
On Thu, Jun 20, 2013 at 12:35 AM, Christer Solskogen
wrote:
> On 19.06.2013 11:37, Dongsheng Song wrote:
>> I can build i686-w64-mingw32-gcc and x86_64-w64-mingw32-gcc under
>> Linux, but when I use this compiler to compile native Windows
>> compiler, gcc 4.7 success, gcc 4.8 failed with same buil
On 19.06.2013 11:37, Dongsheng Song wrote:
> I can build i686-w64-mingw32-gcc and x86_64-w64-mingw32-gcc under
> Linux, but when I use this compiler to compile native Windows
> compiler, gcc 4.7 success, gcc 4.8 failed with same build script like
> this:
>
> make[2]: Entering directory `/home/cauch
Hi Geoffroy,
On 06/17/13 18:42, Geoffroy Couprie wrote:
> Hi,
>
> I am currently working on writing the IDL files for new WinRT
> interfaces (mostly Windows.Storage and Windows.Foundation for now),
> and there are a few things I would need to make it work. Right now, I
> can comment out the proble
On Jun 19 15:24, Corinna Vinschen wrote:
> On Jun 19 14:14, Ray Donnelly wrote:
> > On Wed, Jun 19, 2013 at 2:05 PM, Corinna Vinschen wrote:
> > > Btw., this is one reason why I don't understand the desire to use native
> > > tools. If you can get a working POSIXy build environment for free, why
>
On Jun 19 15:27, Ruben Van Boxem wrote:
> 2013/6/19 Corinna Vinschen
> > And there's another problem with this approach. Unfortunately you can't
> > overwrite symlinks atomically. You have to remove the old symlink and
> > create a new one. In the time between removing and recreation, another
>
2013/6/19 Corinna Vinschen
> On Jun 19 14:11, Ruben Van Boxem wrote:
> > 2013/6/19 LRN
> >
> > > -BEGIN PGP SIGNED MESSAGE-
> > > Hash: SHA1
> > >
> > > On 19.06.2013 15:54, Ruben Van Boxem wrote:
> > > > 2013/6/19 Corinna Vinschen
> > > >
> > > >> On Jun 19 12:34, Corinna Vinschen wrot
On Jun 19 14:14, Ray Donnelly wrote:
> On Wed, Jun 19, 2013 at 2:05 PM, Corinna Vinschen wrote:
> > Btw., this is one reason why I don't understand the desire to use native
> > tools. If you can get a working POSIXy build environment for free, why
> > do you want to use native tools which only gen
Usually it's because Cygwin is usually a lot slower than native for IO
heavy operations. Projects (such as the Android NDK) that supply
Cygwin-based compilers usually try to migrate to native ASAP, viewing the
Cygwin-based tools as a stop-gap measure.
On Wed, Jun 19, 2013 at 2:05 PM, Corinna Vins
On Jun 19 14:36, Corinna Vinschen wrote:
> On Jun 19 16:01, LRN wrote:
> > Cygwin emulates untyped linking (ln -s) by checking the type of the
> > target and creating the link of the right type. If the target doesn't
> > exist, you're screwed.
>
> Not really screwed. But if the target doesn't exi
On Jun 19 14:11, Ruben Van Boxem wrote:
> 2013/6/19 LRN
>
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> >
> > On 19.06.2013 15:54, Ruben Van Boxem wrote:
> > > 2013/6/19 Corinna Vinschen
> > >
> > >> On Jun 19 12:34, Corinna Vinschen wrote:
> > >>> On Jun 19 14:28, LRN wrote:
> >
On 6/19/2013 20:11, Ruben Van Boxem wrote:
>
>> Call me naive, but why not create the link to non-existent ... thing (which
>> should possible, just choose file or directory; it doesn't matter because
>> its not there)... then when the actual thing is created, change the link to
>> conform to the
On Jun 19 16:01, LRN wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 19.06.2013 15:54, Ruben Van Boxem wrote:
> > 2013/6/19 Corinna Vinschen
> >
> >> On Jun 19 12:34, Corinna Vinschen wrote:
> >>> On Jun 19 14:28, LRN wrote:
> [...]
> and that you're using winsymlinks:n
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 19.06.2013 16:11, Ruben Van Boxem wrote:
> 2013/6/19 LRN
>
> On 19.06.2013 15:54, Ruben Van Boxem wrote:
>> 2013/6/19 Corinna Vinschen
>>>
On Jun 19 12:34, Corinna Vinschen wrote:
> On Jun 19 14:28, LRN wrote:
>> [...]
>> and tha
2013/6/19 LRN
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 19.06.2013 15:54, Ruben Van Boxem wrote:
> > 2013/6/19 Corinna Vinschen
> >
> >> On Jun 19 12:34, Corinna Vinschen wrote:
> >>> On Jun 19 14:28, LRN wrote:
> [...]
> and that you're using winsymlinks:nativestrict?
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 19.06.2013 15:54, Ruben Van Boxem wrote:
> 2013/6/19 Corinna Vinschen
>
>> On Jun 19 12:34, Corinna Vinschen wrote:
>>> On Jun 19 14:28, LRN wrote:
[...]
and that you're using winsymlinks:nativestrict?
>>>
>>> No. I'm using any one of t
2013/6/19 Corinna Vinschen
> On Jun 19 12:34, Corinna Vinschen wrote:
> > On Jun 19 14:28, LRN wrote:
> > > -BEGIN PGP SIGNED MESSAGE-
> > > Hash: SHA1
> > >
> > > On 19.06.2013 13:55, Corinna Vinschen wrote:
> > > > On Jun 19 13:32, LRN wrote:
> > > >> On 19.06.2013 12:57, Corinna Vinsch
On Jun 19 12:34, Corinna Vinschen wrote:
> On Jun 19 14:28, LRN wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> >
> > On 19.06.2013 13:55, Corinna Vinschen wrote:
> > > On Jun 19 13:32, LRN wrote:
> > >> On 19.06.2013 12:57, Corinna Vinschen wrote:
> > >>> On Jun 19 12:08, LRN wrote
On Jun 19 14:28, LRN wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 19.06.2013 13:55, Corinna Vinschen wrote:
> > On Jun 19 13:32, LRN wrote:
> >> On 19.06.2013 12:57, Corinna Vinschen wrote:
> >>> On Jun 19 12:08, LRN wrote:
> To be fair here, i've tried the MSYS=winsymlinks
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 19.06.2013 13:55, Corinna Vinschen wrote:
> On Jun 19 13:32, LRN wrote:
>> On 19.06.2013 12:57, Corinna Vinschen wrote:
>>> On Jun 19 12:08, LRN wrote:
To be fair here, i've tried the MSYS=winsymlinks:nativestrict, and first
thing i hit wa
On Jun 19 13:32, LRN wrote:
> On 19.06.2013 12:57, Corinna Vinschen wrote:
> > On Jun 19 12:08, LRN wrote:
> >> To be fair here, i've tried the MSYS=winsymlinks:nativestrict, and first
> >> thing i hit was AC_PROG_LN_S. That macro explicitly refuses to use `ln
> >> - -s' provided by MSYS or Cygwin,
I can build i686-w64-mingw32-gcc and x86_64-w64-mingw32-gcc under
Linux, but when I use this compiler to compile native Windows
compiler, gcc 4.7 success, gcc 4.8 failed with same build script like
this:
make[2]: Entering directory `/home/cauchy/obj/native/gcc-4.8-win32/gcc/gcc'
g++ -c -g -O2 -D
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 19.06.2013 12:57, Corinna Vinschen wrote:
> On Jun 19 12:08, LRN wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> On 12.06.2013 18:51, Alexpux wrote:
>>> среда, 12 июня 2013 г. в 18:00, Corinna Vinschen написал:
On Jun 12 15:50,
On Jun 19 12:08, LRN wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 12.06.2013 18:51, Alexpux wrote:
> > среда, 12 июня 2013 г. в 18:00, Corinna Vinschen написал:
> >> On Jun 12 15:50, Alexpux wrote:
> >>> среда, 12 июня 2013 г. в 14:47, Corinna Vinschen написал:
> On Jun 11
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12.06.2013 18:51, Alexpux wrote:
> среда, 12 июня 2013 г. в 18:00, Corinna Vinschen написал:
>> On Jun 12 15:50, Alexpux wrote:
>>> среда, 12 июня 2013 г. в 14:47, Corinna Vinschen написал:
On Jun 11 21:10, Алексей Павлов wrote:
> 4. Replac
27 matches
Mail list logo
