Messages

1

General discussions / Re: Android and iOS ports available for testing

« on: December 29, 2015, 05:03:01 pm »

Maybe You don't have permissions to write to that file? Try that:

<manifest ...>
    <uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" />
    ...
</manifest>

2

General discussions / Re: Android and iOS ports available for testing

« on: December 05, 2015, 10:27:25 pm »

Well, no, I think You're mistaking assets with resources now I'm not too familiar with whole android apk structure, but as far as I understood, strings get compiled with other resources description to resources.arsc and when You're creating a "standard" android apk You simply use @string/app_name to get app_name string, depending on user's language. It could be a neat feature for SFML(if that's even possible through native functions).

3

General discussions / Re: Android and iOS ports available for testing

« on: December 05, 2015, 01:04:18 pm »

Thanks, that solved it Getting string from resources is also not possible directly through SFML right now?

4

General discussions / Re: Android and iOS ports available for testing

« on: December 04, 2015, 05:39:56 pm »

Sure,

window.draw(rectangle, 4, sf::Quads);

this works on windows but does not on android.

5

General discussions / Re: Android and iOS ports available for testing

« on: December 04, 2015, 05:27:48 pm »

Another thing - sf::Vertex seems to be not rendering on Android. Is that a known bug?

6

General discussions / Re: Android and iOS ports available for testing

« on: November 30, 2015, 07:43:35 pm »

Thank You both for Your answers I was looking at AssetManager examples before, but does even SFML give access to the required handles(JNIEnv* env, jobject clazz --- if that's even required or I did not understand the examples)?

7

General discussions / Re: Android and iOS ports available for testing

« on: November 30, 2015, 02:18:20 pm »

Hello! Quick question - is there any SF-way to get dir structure inside of apk assets?
If not - do You know any? I tried dirent.h, but it's not working inside of apk.

8

SFML projects / Re: SFNUL

« on: April 12, 2015, 03:05:06 pm »

I uninstalled GitHub, installed Git and everything worked as charm!

Thank You both, gentlemen!

9

SFML projects / Re: SFNUL

« on: April 12, 2015, 11:08:16 am »

Instead of working around a problem, you should really try fixing it.

Yeah, I'd love to, just couldn't find any solution, so I just sadly accepted the fact that windows version of github has its charms ;p error is:

fatal: 'submodule' appears to be a git command, but we were not
able to execute it. Maybe git-submodule is broken?

I've found some questions about it, no solution though.

This sounds even more troubling... What kind of a patch was this? And what did/didn't work? If anything doesn't work, at least ask for assistance before applying random patches to the base installation. They might end up breaking more things than they fix.

http://tehsausage.com/mingw-to-string
Well, it seems to have worked for me

There is nothing wrong with SFNUL, but there are many things wrong with your development environment as stated above.

Hahah yeah I know, I was just messing with You SFML handled it though!

Rewind (reinstall MinGW if necessary), and go back to the "git submodule doesn't work for me" stage and provide some error information. That is a starting point that we will be able to work with.

Yeah, I'll start with reinstalling MinGW and/or building with another version.
Thanks for the support

10

General discussions / Re: Android and iOS ports available for testing

« on: April 12, 2015, 10:44:21 am »

Yep, nothing changed over here.

11

General discussions / Re: Android and iOS ports available for testing

« on: April 12, 2015, 10:05:02 am »

How can I check it? It doesn't say in the LogCat.

BTW I'm getting "Fatal signal 11 (SIGSEGV) at 0x00000028 (code=1), thread 26308" when I close the app.

12

SFML projects / Re: SFNUL

« on: April 12, 2015, 10:01:09 am »

Hey there,
I'm really fighting hard to build SFNUL and see all that awesomeness, but it's just not letting me.
First of all - git submodule isn't working for me, so I cloned the dependencies by myself.
Secondly - had some problems with mingw headers, but found patch which fixed it.
Now I'm already at 89% and it's throwing errors at my face again:

E:\Projects\SFNUL\src\SFNUL\NetworkResource.cpp:35:10: error: invalid use of tem
plate-name 'asio::strand' without an argument list
  mutable asio::strand strand;
          ^
E:\Projects\SFNUL\src\SFNUL\NetworkResource.cpp: In constructor 'sfn::NetworkRes
ource::NetworkResourceImpl::NetworkResourceImpl()':
E:\Projects\SFNUL\src\SFNUL\NetworkResource.cpp:26:3: error: class 'sfn::Network
Resource::NetworkResourceImpl' does not have any field named 'strand'
   strand{ *io_service }
   ^
E:\Projects\SFNUL\src\SFNUL\NetworkResource.cpp: In member function 'void* sfn::
NetworkResource::GetStrand() const':
E:\Projects\SFNUL\src\SFNUL\NetworkResource.cpp:51:18: error: 'class sfn::Networ
kResource::NetworkResourceImpl' has no member named 'strand'
  return &m_impl->strand;
                  ^
E:\Projects\SFNUL\src\SFNUL\NetworkResource.cpp:52:1: warning: control reaches e
nd of non-void function [-Wreturn-type]
 }
 ^
CMakeFiles\sfnul.dir\build.make:4614: recipe for target 'CMakeFiles/sfnul.dir/sr
c/SFNUL/NetworkResource.cpp.obj' failed
mingw32-make[2]: *** [CMakeFiles/sfnul.dir/src/SFNUL/NetworkResource.cpp.obj] Er
ror 1
CMakeFiles\Makefile2:59: recipe for target 'CMakeFiles/sfnul.dir/all' failed
mingw32-make[1]: *** [CMakeFiles/sfnul.dir/all] Error 2
Makefile:115: recipe for target 'all' failed
mingw32-make: *** [all] Error 2

I'm using TDM GCC 4.9.2 DW2 and I successfully built SFML, SFGUI and all other goodness under it, so what's wrong with SFNUL? Also, doesn't that whole "asio" need to be built? It's not included in CMakeLists. Thanks!

13

General discussions / Re: Android and iOS ports available for testing

« on: April 12, 2015, 09:38:16 am »

Yeah, well it shows some "Failed to activate window's context" and "called unimplemented OpenGL ES API"(even when it works just fine). It usually crashes when i close my app and try to run it again in short period of time. And sound is still not working ;p

I'm using my device(Samsung Galaxy SIII with Android 4.1.2(16) directly by usb cable. Even tried downgrading target level to 16, but I guess it doesn't even make any sense to do so.

14

General discussions / Re: Android and iOS ports available for testing

« on: April 12, 2015, 12:42:23 am »

Thanks for Your responses. I'm using newest NDK avaible(r10d), 4.4.2(19) as a target, 9 as min(I guess that's standard config from example), nothing fancy. Also - sometimes the SFML window just don't get open - app stucks on the default theme background; sometimes it even crashes whole android. Any ideas?

15

General discussions / Re: Android and iOS ports available for testing

« on: April 05, 2015, 08:52:16 pm »

Well, I built everything with the official instructions, from the newest master version and used the android example as a base. There was sound file and music with that example, none of them worked.