We are currently migrating Bugzilla to GitHub issues.
Any changes made to the bug tracker now will be lost, so please do not post new bugs or make changes to them.
When we're done, all bug URLs will redirect to their equivalent location on the new bug tracker.

Bug 2890 - cross platform project template
Summary: cross platform project template
Status: RESOLVED ABANDONED
Alias: None
Product: SDL
Classification: Unclassified
Component: *don't know* (show other bugs)
Version: HG 2.1
Hardware: x86_64 Linux
: P2 normal
Assignee: Ryan C. Gordon
QA Contact: Sam Lantinga
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-02-25 20:31 UTC by Johan Euphrosine
Modified: 2018-08-06 21:20 UTC (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Johan Euphrosine 2015-02-25 20:31:00 UTC 
Currently the source tree contains project template for android and iOS, each pointing to a different demo application:
http://hg.libsdl.org/SDL/file/b577c4753421/android-project/jni/src/Android.mk#l13
http://hg.libsdl.org/SDL/file/b577c4753421/Xcode-iOS/Template/SDL%20iOS%20Application

It would be nice if those were organized in a way that you can build the same demo for multiple platforms, something like:
SDL/template/
SDL/template/main.c
SDL/template/ios/template.xcodeproj
SDL/template/android/jni/Android.mk
SDL/template/desktop/CMakeLists.txt

I did a proof of concept here:
https://github.com/proppy/native-sdl-starter-kit

You can check that it's building there:
https://travis-ci.org/proppy/native-sdl-starter-kit/

Let me know if you would welcome a patch to re-organize the sample in a similar way.
Comment 1 Sam Lantinga 2016-10-07 23:47:11 UTC 
Sure, that would be great.

Thanks!
Comment 2 Ryan C. Gordon 2018-08-06 21:20:20 UTC 
Hello, and sorry if you're getting dozens of copies of this message by email.

We are closing out bugs that appear to be abandoned in some form. This can happen for lots of reasons: we couldn't reproduce it, conversation faded out, the bug was noted as fixed in a comment but we forgot to mark it resolved, the report is good but the fix is impractical, we fixed it a long time ago without realizing there was an associated report, etc.

Individually, any of these bugs might have a better resolution (such as WONTFIX or WORKSFORME or INVALID) but we've added a new resolution of ABANDONED to make this easily searchable and make it clear that it's not necessarily unreasonable to revive a given bug report.

So if this bug is still a going concern and you feel it should still be open: please feel free to reopen it! But unless you respond, we'd like to consider these bugs closed, as many of them are several years old and overwhelming our ability to prioritize recent issues.

(please note that hundred of bug reports were sorted through here, so we apologize for any human error. Just reopen the bug in that case!)

Thanks,
--ryan.