Dear colleagues,
It seems to me, something was happened with cross-compilation on MacOS. I have
successfully built all libraries for 32-bit ARM architecture and then built
applications and libraries on Ubuntu 15 with x86_64 Swift compiler, pointing
out --target=armv7-unknown-linux-gnueabi and pl
d where this part is
analyzed in compiler source code? Thanks in advance for answer this interesting
question.
17.03.2016, 22:32, "Труб Илья via swift-dev" :
> Dear colleagues,
> It seems to me, something was happened with cross-compilation on MacOS. I
> have successf
Dear colleagues
I have faced with strange behaviour, when I compile some swift source on Ubuntu
14, target=arm-linux-gnueabi, all neccessary modules for arm present, -sysroot
and
-isysroot are passed via -Xcc.
:61:10: note: in file included from :61:
#include "/usr/include/x86_64-linux-gnu/sys
Thanks for your answer, Dmitry. I will look for examples of module maps in test
sources.
24.03.2016, 23:56, "Dmitri Gribenko" :
> On Thu, Mar 24, 2016 at 1:30 PM, Труб Илья wrote:
>> Dear colleagues
>> I have faced with strange behaviour, when I compile some swift source on
>> Ubuntu 14, targ
I have built all targets for arm (including modules and libraries) within the
native arm environment on arm-emulator with chroot.
25.03.2016, 00:25, "Dmitri Gribenko" :
> On Thu, Mar 24, 2016 at 2:03 PM, Труб Илья wrote:
>> Thanks for your answer, Dmitry. I will look for examples of module maps
Yes, Dmitry. I found corresponding module.map for arm and placed it into glibs
subdirectory of my swiftc's include path. It was found. But, it seems to me,
sysroot argument is not applied to paths, written in that module.map or I do
not how to correct do that.
I add to swift command-line followi
;
File = SourceMgr.getFileManager().getFile(RelativePathName);
}
We can see, that sysroot (or isysroot) argument is ignored. What can you say
about that?
25.03.2016, 12:21, "Труб Илья via swift-dev" :
> Yes, Dmitry. I found corresponding module.map for arm and placed it into
> glibs