StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
18842393
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-09-17T06:06:26.770
FavoriteCount
0
LastActivityDate
2013-09-17T06:18:26.997
LastEditDate
2013-09-17T06:18:26.997
LastEditorUserId
2359247
OwnerUserId
2359247
ParentId
18832788
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
You have multiple options here assuming that you have a first.cpp file that you implemented the Test class correctly. Without being able to see your Android.mk, I will go through all options: Build First.cpp as a static or shared library and add this library to your module which compiles Second.cpp. Your Android.mk should look like: <pre><code>LOCAL_PATH:= $(call my-dir) include $(CLEAR_VARS) LOCAL_MODULE := firstlib LOCAL_C_INCLUDES := path/to/first.h LOCAL_SRC_FILES := first.cpp include $(BUILD_STATIC_LIBRARY) </code></pre> If you would like First to be a shared library instead of a static library, change include $(BUILD_STATIC_LIBRARY) line to: <pre><code>include $(BUILD_SHARED_LIBRARY) </code></pre> Now, your second lib is compiled as follows: <pre><code>include $(CLEAR_VARS) LOCAL_MODULE := second LOCAL_C_INCLUDES := path/to/first.h LOCAL_C_INCLUDES += path/to/second.h LOCAL_SRC_FILES := second.cpp LOCAL_STATIC_LIBRARIES := firstlib include $(BUILD_SHARED_LIBRARY) </code></pre> If firstlib is built as shared library, you can link it by chaning LOCAL_STATIC_LIBRARIES += firstlib line to the following: <pre><code>LOCAL_SHARED_LIBRARIES += firstlib </code></pre> As a second solution, you can build first.cpp as a part of the second lib and this way you don't have to worry about linking against the first library. This is more like a design choice and how you would like to shape up your libraries: <pre><code>include $(CLEAR_VARS LOCAL_MODULE := libtwolib-second include $(CLEAR_VARS) LOCAL_MODULE := libtwolib-second LOCAL_C_INCLUDES := path/to/first.h LOCAL_C_INCLUDES += path/to/second.h LOCAL_SRC_FILES := first.cpp LOCAL_SRC_FILES += second.cpp include $(BUILD_SHARED_LIBRARY) </code></pre> Finally, you can find a sample of the first approach in your NDK directory, under samples/twolibs.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POAndroid NDK C++ Class undefined Reference
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USeozgonul
UserOwnerUserId
1. USeozgonul
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.