Welcome, Guest. Please login or register. Did you miss your activation email?

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - jheinz

Pages: [1]
1
General / Trouble building arm64-v8a android
« on: April 14, 2016, 10:57:32 pm »
Hey everybody,

I've been using SFML for awhile, and recently I've been looking into creating android apps. Since I'm familiar with SFML, I thought I'd try out the experimental android port. I've managed to compile armeabi and armeabi-v7a targets, but I'm currently trying to figure out how to get arm64-v8a to compile. This is the output of make:
Code: [Select]

Scanning dependencies of target sfml-system
[  1%] Building CXX object src/SFML/System/CMakeFiles/sfml-system.dir/Clock.cpp.o
[  2%] Building CXX object src/SFML/System/CMakeFiles/sfml-system.dir/Err.cpp.o
In file included from (NDK)/platforms/android-21/arch-arm64/usr/include/signal.h:37:0,
                 from (NDK)/platforms/android-21/arch-arm64/usr/include/pthread.h:33,
                 from (NDK)/sources/cxx-stl/llvm-libc++/libcxx/include/__mutex_base:17,
                 from (NDK)/sources/cxx-stl/llvm-libc++/libcxx/include/mutex:176,
                 from (NDK)/sources/cxx-stl/llvm-libc++/libcxx/include/__locale:18,
                 from (NDK)/sources/cxx-stl/llvm-libc++/libcxx/include/ios:216,
                 from (NDK)/sources/cxx-stl/llvm-libc++/libcxx/include/ostream:131,
                 from SFML-2.3.2/include/SFML/System/Err.hpp:32,
                 from SFML-2.3.2/src/SFML/System/Err.cpp:28:
(NDK)/platforms/android-21/arch-arm64/usr/include/asm/sigcontext.h:45:2: error: '__uint128_t' does not name a type
  __uint128_t vregs[32];
  ^
make[2]: *** [src/SFML/System/CMakeFiles/sfml-system.dir/Err.cpp.o] Error 1
make[1]: *** [src/SFML/System/CMakeFiles/sfml-system.dir/all] Error 2
make: *** [all] Error 2


This is the file that generates the error, it appears that even editing it will not do anything (although I may be wrong):

Code: [Select]

/****************************************************************************
 ****************************************************************************
 ***
 ***   This header was automatically generated from a Linux kernel header
 ***   of the same name, to make information necessary for userspace to
 ***   call into the kernel available to libc.  It contains only constants,
 ***   structures, and macros generated from the original header, and thus,
 ***   contains no copyrightable information.
 ***
 ***   To edit the content of this header, modify the corresponding
 ***   source file (e.g. under external/kernel-headers/original/) then
 ***   run bionic/libc/kernel/tools/update_all.py
 ***
 ***   Any manual change here will be lost the next time this script will
 ***   be run. You've been warned!
 ***
 ****************************************************************************
 ****************************************************************************/
#ifndef _UAPI__ASM_SIGCONTEXT_H
#define _UAPI__ASM_SIGCONTEXT_H
#include <linux/types.h>
struct sigcontext {
/* WARNING: DO NOT EDIT, AUTO-GENERATED CODE - SEE TOP FOR INSTRUCTIONS */
 __u64 fault_address;
 __u64 regs[31];
 __u64 sp;
 __u64 pc;
/* WARNING: DO NOT EDIT, AUTO-GENERATED CODE - SEE TOP FOR INSTRUCTIONS */
 __u64 pstate;
 __u8 __reserved[4096] __attribute__((__aligned__(16)));
};
struct _aarch64_ctx {
/* WARNING: DO NOT EDIT, AUTO-GENERATED CODE - SEE TOP FOR INSTRUCTIONS */
 __u32 magic;
 __u32 size;
};
#define FPSIMD_MAGIC 0x46508001
/* WARNING: DO NOT EDIT, AUTO-GENERATED CODE - SEE TOP FOR INSTRUCTIONS */
struct fpsimd_context {
 struct _aarch64_ctx head;
 __u32 fpsr;
 __u32 fpcr;
/* WARNING: DO NOT EDIT, AUTO-GENERATED CODE - SEE TOP FOR INSTRUCTIONS */
 __uint128_t vregs[32];
};
#endif


If anyone has a clue how to get around this, that'd be awesome. Thanks!

2
General discussions / Re: Looking for a dev partner
« on: March 30, 2016, 01:57:29 am »
I'm totally interested. I'm exactly in your position; Self-taught w/ about 5 years practice on and off. I've started a good few projects, but like you, I've never finished any of them due to lack of motivation. I'm in the United States, so that may be an issue, but if not I'd love to do some collaboration. I can put at least 10 hours a week into it. Let me know if this sounds good!

Pages: [1]
anything