Hi,
I sometimes use java System.getProperty() & System.setProperty() as an
alternative to environment variables eg -
System.setProperty("DEBUG", debug);
and
if (System.getProperty("DEBUG","0").equals("1")) Log.w("abc", "123");
They seem to be available across activities & threads within the sa
On Thu, Sep 29, 2011 at 10:11 AM, petr.maza...@mautilus.com
wrote:
> I agree that environmental variables might not be the best approach,
> but we are porting software, which is expected to use it.
Then fix the software to not use environment variables.
For example, if this is C/C++ code, as par
Hi,
I agree that environmental variables might not be the best approach,
but we are porting software, which is expected to use it. So, there is
no way for one process/thread to set environmental variables, which
can be read by other one? What about calling from the java application
the .so library
what are you actually trying to achieve? What are you planning to use the
environment variables for?
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe fr
4 matches
Mail list logo
