Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I did something similar (but not for this reason) which required updating the manifest at build time. The way I accomplished this was by making a second AndroidManifest and putting it under a directory named config. So in config/AndroidManifest you could have something like this:</p> <pre><code>&lt;manifest xmlns:android="http://schemas.android.com/apk/res/android" package="@CONFIG.APP_PACKAGE_NAME@" android:versionCode="@CONFIG.APP_VERSION_CODE@" android:versionName="@CONFIG.APP_VERSION@"&gt; &lt;!-- EVERYTHING ELSE GOES HERE --&gt; &lt;/manifest&gt; </code></pre> <p>Then you can use the regular bare bones build.xml ant script with just a few modifications (no need to copy the whole script from the android build system as they added some hooks for you to use without reinventing the wheel). The build script should be reading local.properties by default, but if not add (or uncomment) a line like this:</p> <pre><code>&lt;property file="local.properties" /&gt; </code></pre> <p>In your build script you should see a task called "-pre-build", change it like this:</p> <pre><code>&lt;target name="-pre-build"&gt; &lt;copy file="config/AndroidManifest.xml" todir="." overwrite="true" encoding="utf-8"&gt; &lt;filterset&gt; &lt;filter token="CONFIG.APP_PACKAGE_NAME" value="${app.packagename}" /&gt; &lt;filter token="CONFIG.APP_VERSION" value="${app.version}" /&gt; &lt;filter token="CONFIG.APP_VERSION_CODE" value="${app.versioncode}" /&gt; &lt;/filterset&gt; &lt;/copy&gt; &lt;/target&gt; </code></pre> <p>Then your local.properties file you would put the package name, version name/code like so:</p> <pre><code>app.version=1.0 app.versioncode=1 app.packagename=com.mypackage.name </code></pre> <p>Now you just need to make sure in your manifest that you fully qualify all of your activities/services/broadcast listeners etc.. That means you always specify the full package of your source code. If you want the package for your own source code to be dynamic you could replace out each of the prefixes to each class.. But that seems kind of silly.. It is easy enough to package your code up under your own package name and they can use it from any project by simply including the source or a jar in their project.</p> <p>-- UPDATE -- Oh and one other thing you can do to notify the user that they must define a package name is use the fail tag in your build xml like this:</p> <pre><code>&lt;fail message="app.packagename is missing. This must be defined in your local.properties file" unless="app.packagename" /&gt; </code></pre> <p>Put this after the line which reads the local.properties file</p>
    singulars
    1. This table or related slice is empty.
    1. POAndroid - How do I dynamically set the package name at build time for an Open-source project?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USMatt Wolfe
    1. USMatt Wolfe
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTApproveEditSuggestion
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COAh, my build script (generated by android update), _is_ 'barebones' and contains `<import file="${sdk.dir}/tools/ant/build.xml" />`. So I can commit this file to the repo with some modifications. Right, let me see...
      singulars
      1. PO
      1. USJames Haigh
    2. COYeah some people say its a bad idea but I've been doing it for well over a year without any issues. They obviously leave those hooks for you but there isn't any guarantee that in the next android version they could change things. IIRC the other thing I had to do for it to play nice with Eclipse was add: <import file="${sdk.dir}/tools/ant/build.xml" as="androidbuild" /> However for the changes above you shouldn't need this. I only needed it so that I could reuse some of the targets in the tools/ant/build.xml from my script, and to do that I would then just had to use androidbuild.[targetname]
      singulars
      1. PO
      1. USMatt Wolfe
    3. COIf i didn't have the "as=androidbuild" section then eclipse would complain that the targets didn't exist and eclipse would fail to build my project even though I wasn't using my ant script from eclipse in the first place.
      singulars
      1. PO
      1. USMatt Wolfe
 

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.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload