llvm dev - Nov 2015 - can't compile llvm source on Windows Mobile

Hi,

The current LLVM source can't be compiled on Windows 10 Mobile because it
uses some Windows APIs that are not available on mobile platform.
Below is a detail example. I would like to get your suggestion on how to
work-around this or fix it properly.

This API is tagged as desktop only:    CreateJobObjectW, see
https://msdn.microsoft.com/en-us/library/windows/desktop/ms682409(v=vs.85).aspx
It is used in lib/Support/Windows/Program.inc, then used in
lib\Support\Program.cpp and llvm::DisplayGraph indirectly.

Thanks!

Bixia


________________________________

-- IMPORTANT NOTICE: The contents of this email and any attachments are
confidential and may also be privileged. If you are not the intended recipient,
please notify the sender immediately and do not disclose the contents to any
other person, use it for any purpose, or store or copy the information in any
medium. Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20151102/fcf372d5/attachment.html>

On 2 Nov 2015, at 19:35, Bixia Zheng via llvm-dev <llvm-dev at
lists.llvm.org> wrote:
> 
> The current LLVM source can’t be compiled on Windows 10 Mobile because it
uses some Windows APIs that are not available on mobile platform.
> Below is a detail example. I would like to get your suggestion on how to
work-around this or fix it properly.
>  
> This API is tagged as desktop only:    CreateJobObjectW, see
https://msdn.microsoft.com/en-us/library/windows/desktop/ms682409(v=vs.85).aspx
> It is used in lib/Support/Windows/Program.inc, then used in
lib\Support\Program.cpp and llvm::DisplayGraph indirectly.
If the only place that this is used is in DisplayGraph then it’s probably safe
to simply #ifdef it out for Windows Mobile.  That API is intended to only be
used when debugging, and the kind of debugging environment doesn’t really make
sense for a mobile device that doesn’t have the debugger / toolchain running
locally.  It would probably be worth modifying DisplayGraph to dump the contents
of the .dot file in the debugger, when it is not possible to run other programs.

David