[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-windows
Subject: Re: Build manually for MSVC2008
From: Zeke Connor <xzekecomax () gmail ! com>
Date: 2009-05-29 16:46:12
Message-ID: 85b2058c0905290946k7ee62a60o7317f99f80dd489f () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
What about the precompiled binaries for 7.1, 8.0, 9.0 here?
http://www.boostpro.com/download.
Can't we simple just use these instead?
On Fri, May 29, 2009 at 5:51 AM, Patrick Spendrin <ps_ml@gmx.de> wrote:
> Andreas Pakulat schrieb:
> > On 29.05.09 10:40:18, Patrick Spendrin wrote:
> >> Andreas Pakulat schrieb:
> >>> Hi,
> >>>
> >>> I've now setup a VMware to do some windows-development for KDevelop4
> and
> >>> as I understood from previous emails its a bit of work, but probably
> >>> better to build with MSVC2008.
> >>>
> >>> Now the question arises: How to I prevent emerge from fetching binary
> >>> packages? If I cannot do that, is there some docs how I create binary
> >>> packages myself and lets emerge use them (apart from the source code)?
> >>> And last but not least: Does anybody have a list of packages where
> >>> emerge downloads the binary instead of compiling it?
> >> Well, the point is that in most cases you don't even need to recompile
> >> the binary packages - older libraries will be understood by the newer
> >> compiler. The biggest problem is that the boost binary package doesn't
> >> contain libraries for 2k8 compiler and thus needs to be recompiled.
> >
> > As far as I understand our windows experts here at work, mixing different
> > runtime libraries inside the same application can be problematic -
> causing
> > strange crashes etc.
> >
> > I'd like to avoid hunting down crashes that are possibly caused by such
> > mixing.
> >
> As long as you keep away from installing the old runtime (the redist
> package from the installer), you should be save. The runtime libraries
> are used from your compiler then.
> If that would be not correct, you would have to recompile at least the
> dbus and pcre packages (all C++ packages, there are more like libchm,
> libmsn but those are not needed for kdevelop iirc).
> >> This should be about the only compiler related problem so far.
> >> As this is about to change in the coming days (boost package will be
> >> packaged), this how-to is really only temporary.
> >
> > Yeah, I just can't wait :)
> np, just go ahead and use this weekends time :-D.
> >
> > Andreas
> >
>
> _______________________________________________
> Kde-windows mailing list
> Kde-windows@kde.org
> https://mail.kde.org/mailman/listinfo/kde-windows
>
[Attachment #5 (text/html)]
What about the precompiled binaries for 7.1, 8.0, 9.0 here? <a \
href="http://www.boostpro.com/download">http://www.boostpro.com/download</a>.<br>Can't \
we simple just use these instead?<br><br><div class="gmail_quote">On Fri, May 29, \
2009 at 5:51 AM, Patrick Spendrin <span dir="ltr"><<a \
href="mailto:ps_ml@gmx.de">ps_ml@gmx.de</a>></span> wrote:<br> <blockquote \
class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt \
0pt 0.8ex; padding-left: 1ex;">Andreas Pakulat schrieb:<br> <div class="im">> On \
29.05.09 10:40:18, Patrick Spendrin wrote:<br> >> Andreas Pakulat schrieb:<br>
>>> Hi,<br>
>>><br>
>>> I've now setup a VMware to do some windows-development for KDevelop4 \
and<br> >>> as I understood from previous emails its a bit of work, but \
probably<br> >>> better to build with MSVC2008.<br>
>>><br>
>>> Now the question arises: How to I prevent emerge from fetching \
binary<br> >>> packages? If I cannot do that, is there some docs how I \
create binary<br> >>> packages myself and lets emerge use them (apart from \
the source code)?<br> >>> And last but not least: Does anybody have a list \
of packages where<br> >>> emerge downloads the binary instead of compiling \
it?<br> >> Well, the point is that in most cases you don't even need to \
recompile<br> >> the binary packages - older libraries will be understood by \
the newer<br> >> compiler. The biggest problem is that the boost binary package \
doesn't<br> >> contain libraries for 2k8 compiler and thus needs to be \
recompiled.<br> ><br>
> As far as I understand our windows experts here at work, mixing different<br>
> runtime libraries inside the same application can be problematic - causing<br>
> strange crashes etc.<br>
><br>
> I'd like to avoid hunting down crashes that are possibly caused by such<br>
> mixing.<br>
><br>
</div>As long as you keep away from installing the old runtime (the redist<br>
package from the installer), you should be save. The runtime libraries<br>
are used from your compiler then.<br>
If that would be not correct, you would have to recompile at least the<br>
dbus and pcre packages (all C++ packages, there are more like libchm,<br>
libmsn but those are not needed for kdevelop iirc).<br>
<div class="im">>> This should be about the only compiler related problem so \
far.<br> >> As this is about to change in the coming days (boost package will \
be<br> >> packaged), this how-to is really only temporary.<br>
><br>
> Yeah, I just can't wait :)<br>
</div>np, just go ahead and use this weekends time :-D.<br>
><br>
> Andreas<br>
<div><div></div><div class="h5">><br>
<br>
_______________________________________________<br>
Kde-windows mailing list<br>
<a href="mailto:Kde-windows@kde.org">Kde-windows@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/kde-windows" \
target="_blank">https://mail.kde.org/mailman/listinfo/kde-windows</a><br> \
</div></div></blockquote></div><br>
_______________________________________________
Kde-windows mailing list
Kde-windows@kde.org
https://mail.kde.org/mailman/listinfo/kde-windows
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic