On Sun, 26 Jul 2015, Steve Lhomme wrote:
On Sun, Jul 26, 2015 at 12:00 PM, Martin Storsjö <[email protected]> wrote:
On Sun, 26 Jul 2015, Martin Storsjö wrote:
---
After these patches, one can do a build for Windows Phone/ARM with
as little configure flags as this:
--toolchain=msvc --target-os=win32 --enable-cross-compile --arch=arm
--cpu=armv7-a --extra-cflags='-DWINAPI_FAMILY=WINAPI_FAMILY_PHONE_APP'
---
configure | 14 ++++++++++++++
1 file changed, 14 insertions(+)
Steve, hopefully these patches won't cause any issues when building with
VLC's compiler wrapper script. The one that adds -MD might be a bit messy
since it just checks what's in CFLAGS (and won't know if you have anything
extra automatically added in the wrapper that configure doesn't know of),
but other than that, most of these things should work seamlessly with
existing setups (with lots of hardcoded flags) and allow removing a lot of
the boilerplate flags.
No they shouldn't. Also your patch doesn't take in account WinRT which
is a little bit different.
Check https://github.com/robUx4/vlc-msvc/blob/master/wrappers/clwrap#L13
Which ones of those are strictly necessary for libav? When targeting
WinRT, building right now works just fine without adding any extra
ldflags. As long as we don't call any such APIs, one doesn't need to add
e.g. RuntimeObject.lib or any such. The only thing that would be useful is
adding the nodefaultlib entries, but I don't really see why they'd be
necessary here either.
(Also, it feels weird that you're first forcing both ole32.lib and
kernel32.lib and then adding -nodefaultlib to exclude them again.)
Or am I missing anything? I haven't actually tried shipping any WinRT app.
// Martin
_______________________________________________
libav-devel mailing list
[email protected]
https://lists.libav.org/mailman/listinfo/libav-devel
