Cool thanks folks! Since http://buildbot.wireshark.org/trunk/waterfall shows
failed on both wireshark win32 and win64, I'll hold off on my svn update
until later tonight when both are green.
On Wed, Mar 11, 2009 at 12:18 PM, Gerald Combs <ger...@wireshark.org> wrote:

> You should now, along with updating SVN. I just checked in a change to use
> WIRESHARK_TARGET_PLATFORM (note the fixed spelling) instead of PLATFORM.
>
> Config.nmake sets CPU according to WIRESHARK_TARGET_PLATFORM. You shouldn't
> have
> to set it yourself.
>
> Brian Daniel wrote:
> > Yep, turns out I need to keep my setting: Platform=BPC
> > Should I use WIRESHRK_TARGET_PLATFORM=win64 ??
> > For now, I'll try to temporarily change to Platform=win32 or win64 each
> > time I launch the cmd.exe
> >
> > Also, what CPU= should I put for my Intel Core2 Quad Q6600?
> > x86 is a solution for a very old Intel CPU.
> > Many Thanks,
> > Brian
> > On Tue, Mar 10, 2009 at 8:26 PM, Guy Harris <g...@alum.mit.edu
> > <mailto:g...@alum.mit.edu>> wrote:
> >
> >
> >     On Mar 10, 2009, at 5:08 PM, Gerald Combs wrote:
> >
> >     > Should we use something more Wireshark-specific, e.g.
> >     > WIRESHRK_TARGET_PLATFORM
> >     > instead?
> >
> >     That might work better.  When Googling for information about this I
> >     found at least a couple of instances of some annoying bit of software
> >     insisting on setting the PLATFORM environment variable to some silly
> >     string such as BPC or HPC and breaking MSVC++ builds, so if we can
> >     avoid depending on PLATFORM at all, that might at least keep us from
> >     getting hosed by those programs.
> >
> ___________________________________________________________________________
> >     Sent via:    Wireshark-dev mailing list <wireshark-dev@wireshark.org
> >     <mailto:wireshark-dev@wireshark.org>>
> >     Archives:    http://www.wireshark.org/lists/wireshark-dev
> >     Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
> >                 mailto:wireshark-dev-requ...@wireshark.org
> >     <mailto:wireshark-dev-requ...@wireshark.org>?subject=unsubscribe
> >
> >
> >
> > ------------------------------------------------------------------------
> >
> >
> ___________________________________________________________________________
> > Sent via:    Wireshark-dev mailing list <wireshark-dev@wireshark.org>
> > Archives:    http://www.wireshark.org/lists/wireshark-dev
> > Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
> >              mailto:wireshark-dev-requ...@wireshark.org
> ?subject=unsubscribe
>
>
> --
> Join us for Sharkfest’09  |  Stanford University, June 15 – 18
> http://www.cacetech.com/sharkfest.09/
> ___________________________________________________________________________
>  Sent via:    Wireshark-dev mailing list <wireshark-dev@wireshark.org>
> Archives:    http://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
>             mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
>
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@wireshark.org>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Reply via email to