Re: [Wireshark-dev] ARM Build

[Alexis La Goutte]

On Fri, Oct 17, 2014 at 12:19 AM, Guy Harris g...@alum.mit.edu wrote:

 On Oct 16, 2014, at 4:50 AM, Graham Bloice graham.blo...@trihedral.com 
 wrote:

 Visual Studio (VS2013 at least) as 32  64 bit ARM compilers.

 http://msdn.microsoft.com/en-us/library/0w6ke344.aspx

 Type char

 Visual Studio 2013  Other Versions  1 out of 1 rated this helpful 
 - Rate this topic

 The char type is used to store the integer value of a member of the 
 representable character set. That integer value is the ASCII code 
 corresponding to the specified character.

 Microsoft Specific

 Character values of type unsigned char have a range from 0 to 0xFF 
 hexadecimal. A signed char has range 0x80 to 0x7F. These ranges translate to 
 0 to 255 decimal, and –128 to +127 decimal, respectively. *The /J compiler 
 option changes the default from signed to unsigned.*

 END Microsoft Specific

 (emphasis mine, as that seems to implicitly indicate that an unqualified 
 char is signed by default).

 So, unless that page discusses *only* the 
 x86-32/x86-64/Itanium-if-they-still-support-it compilers, it appears that 
 char is signed by default on all platforms, presumably including ARM.

 What we *could* do is, on some platform or platforms, do both default 
 compiles and char-is-unsigned compiles, using /J for MSVC and -funsigned-char 
 with GCC (and Clang?).

 (I couldn't find any -W option for GCC that warns about code that would 
 behave differently with char-is-signed and char-is-unsigned. There should be, 
 but, then, there should also be an option to warn about *all* implicit 
 shortenings - or, at least, all implicit shortenings that aren't known to be 
 safe, such as converting sizeof (int) to a type shorter than size_t - even 
 though there should be.)

Hi Guy,

Thanks, now build without error on ARM hf :-)

@Graham,
May be a good idea to try also with VS2013 on ARM too...
___
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

Re: [Wireshark-dev] ARM Build

[Graham Bloice]

On 18 October 2014 13:26, Alexis La Goutte alexis.lagou...@gmail.com
wrote:

 On Fri, Oct 17, 2014 at 12:19 AM, Guy Harris g...@alum.mit.edu wrote:
 
  On Oct 16, 2014, at 4:50 AM, Graham Bloice graham.blo...@trihedral.com
 wrote:
 
  Visual Studio (VS2013 at least) as 32  64 bit ARM compilers.
 Hi Guy,

 Thanks, now build without error on ARM hf :-)

 @Graham,
 May be a good idea to try also with VS2013 on ARM too...


Maybe not so easy, I tried using CMake (3.02)  but got the following in the
error log where CMake tries to identify the compiler:

Build started 18/10/2014 15:41:44.
Project
E:\Wireshark\build2013arm\CMakeFiles\3.0.2\CompilerIdC\CompilerIdC.vcxproj
on node 1 (default targets).
C:\Program Files
(x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Platforms\ARM\PlatformToolsets\v120\Toolset.targets(36,5):
error MSB8022: Compiling Desktop applications
for the ARM platform is not supported.
[E:\Wireshark\build2013arm\CMakeFiles\3.0.2\CompilerIdC\CompilerIdC.vcxproj]
Done Building Project
E:\Wireshark\build2013arm\CMakeFiles\3.0.2\CompilerIdC\CompilerIdC.vcxproj
(default targets) -- FAILED.

So it looks like Visual Studio can only use the ARM compilers for compiling
Windows Phone\Win RT apps.

There is some discussion on StackOverflow (
http://stackoverflow.com/questions/11151474/can-arm-desktop-programs-be-built-using-visual-studio-2012)
about
ways to fiddle this, but I couldn't get VS2013 to cooperate with 10 minutes
of fiddling.

-- 
Graham Bloice
___
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