StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
3644987
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2010-09-05T04:10:44.600
FavoriteCount
0
LastActivityDate
2010-09-05T04:10:44.600
LastEditDate
LastEditorUserId
0
OwnerUserId
79513
ParentId
3636677
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
(I think some stuff is missing from your jam rules, possibly due to formatting.) Yes, you definitely can define both the debug and production targets with the same rule, using <a href="http://www.boost.org/doc/tools/build/doc/html/bbv2/tutorial/conditions.html" rel="nofollow noreferrer">conditional requirements</a>. An example is even <a href="http://www.boost.org/doc/tools/build/doc/html/bbv2/tasks/installing.html" rel="nofollow noreferrer">the documentation of the <code>install</code> rule</a>. I believe your original rules look like <pre><code>install libCDef : CDef : <install-type>LIB <location>"/home/morpheus/base_install/lib" : <variant>release ; install _libCDef_D : CDef : <install-type>LIB <location>"/home/morpheus/base_install/libdebug" : <variant>debug ; </code></pre> You'll want to make the <code>location</code> feature dependendent on the variant, like so: <pre><code>install libCDef : CDef : <install-type>LIB <variant>release:<location>"/home/morpheus/base_install/lib" <variant>debug:<location>"/home/morpheus/base_install/libdebug" ; </code></pre> As for the second question, yes, <code>use-project</code> would help, although it shouldn't be necessary. You want to do this <pre><code>exe callFSLR : call_FSLR.cpp ../base/CDef//CDef ; </code></pre> <code>../base/CDef//CDef</code> refers to the target named <code>CDef</code> defined in the project (directory) <code>../base/CDef</code>. This refers to the library rule, so boost build will use the version of the library in the bin directory, not the version created by the install rule. (This might matter if you have dynamic library issues.) Also, you don't need the <code>lib CDef</code> immediately above this rule. To avoid the clumsiness of the <code>../base/CDef</code>, you could use the <code>use-project</code> rule to make a new definition for the project. Then should you reorganize the directory structure, you only have one place to change it. <pre><code>use-project /CDef-project : ../base/CDef ; exe callFSLR : call_FSLR.cpp /CDef-project//CDef ; </code></pre> Another possibility, if you are going to use the one target in this one Jamfile, is to use the alias rule. <pre><code>alias CDef : ../base/CDef//CDef ; exe callFSLR : call_FSLR.cpp CDef ; </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POIs it possible to install the debug and release variant of a library with same command?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USAFoglia
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POIs it possible to install the debug and release variant of a library with same command?
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
CommentsPostId
1. COWhen I used the following jamfile : lib CDef : [ glob *.cpp ] : <link>static ; install libCDef : CDef : <install-type>LIB <variant>release:<location>"/home/morpheus/base_install/lib" <variant>debug:<location>"/home/morpheus/base_install/libdebug" ; only the debug variants were built. I deleted the previously compiled release version of the lib but still it was not rebuilt.
 singulars
 PostPostId
 PO
 UserUserId
 USHumble Debugger
2. COMy mistake, I just needed to add ": release debug " after thatfor this to work.
 singulars
 PostPostId
 PO
 UserUserId
 USHumble Debugger

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.