Hi,
On Tue, 16 Sep 2014, Mirko Puliafito wrote:
Thanks for the support Martin.
I used what you suggested with the snapshot source and now I have the
following behaviours:
1) With the config from the fate I get the following configure error:
check_gas using 'armasm' as AS
check_as
BEGIN ./ffconf.wCcGmfBh.S
1 .macro m n, y:vararg=0
2 \n: .int \y
3 .endm
4 m x
END ./ffconf.wCcGmfBh.S
armasm -D_ISOC99_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE
-Dstrtod=avpriv_strtod -Dsnprintf=avpriv_snprintf
-D_snprintf=avpriv_snprintf -Dvsnprintf=avpriv_vsnprintf -nologo -ignore
4509 -DWINAPI_FAMILY=WINAPI_FAMILY_APP -D__ARM_PCS_VFP
-D_WIN32_WINNT=0x0602 -march=armv7-a -c -o ./ffconf.JiBIxDvP.o
./ffconf.wCcGmfBh.S
error A2029: unknown command-line argument or argument value
-D_ISOC99_SOURCE
Usage: armasm [<options>] sourcefile objectfile
armasm [<options>] -o objectfile sourcefile
armasm -h for help
GNU assembler not found, install/update gas-preprocessor
And the configure fails.
Yes - if you want to build the assembly you need to have gas-preprocessor
installed and available in your $PATH. You can get it from
git://git.libav.org/gas-preprocessor.git
If I disable asm "--disable-asm" configure goes on
but I get compilation error on compiling docs. After disabling docs
"disable-doc" everything works fine and I am able to compile.
Ok, that sounds good
2) Trying to link the compiled libs from 1) and using "/MD" on VS 2013 I'm
getting the following:
------ Rebuild All started: Project: TestLibav, Configuration: Release ARM
------
libavformat.a(rtpdec.o) : error LNK2001: unresolved external symbol
__imp_gethostname
It seems a problem of winsock libs somehow. Are they supported on Windows
phone devices?
Yes, they are supported on Windows Phone. However, since you're using
static libraries you need manually add any other extra libs you want to
link it to. In this case, you need to add ws2_32.lib to the list of
additional dependencies within visual studio. (You can also possibly add
--disable-network to the configure line to avoid using this at all.)
Building a shared library might be more convenient though - then you don't
need to keep track of internal details like this. Using a shared library
also simplifies complying with the LGPL in case your application isn't
opensource itself.
// Martin
_______________________________________________
libav-devel mailing list
libav-devel@libav.org
https://lists.libav.org/mailman/listinfo/libav-devel
