Dear Mr Walt61,
thanks for you reply . Possible. PCLINUXOS sticks to SystemV and ManDrake foundation.
Researched the error:
adb.exe F 12-01 11:41:27 239 240 sysdeps_win32.cpp:2743] _wenviron is not set, did you link with -municode?
sysdeps_win32.cpp seems to have to do with UTF16 to UTF8 conversion and back.
Here some code from this sysdeps_win32.cpp , marked the places where mentioned with '====>'
extern "C" int main(int argc, char** argv);
=====> // Link with -municode to cause this wmain() to be used as the program
// entrypoint. It will convert the args from UTF-16 to UTF-8 and call the
// regular main() with UTF-8 args.
extern "C" int wmain(int argc, wchar_t **argv) {
// Convert args from UTF-16 to UTF-8 and pass that to main().
NarrowArgs narrow_args(argc, argv);
return main(argc, narrow_args.data());
}
// Shadow UTF-8 environment variable name/value pairs that are created from
// _wenviron the first time that adb_getenv() is called. Note that this is not
// currently updated if putenv, setenv, unsetenv are called. Note that no
// thread synchronization is done, but we're called early enough in
// single-threaded startup that things work ok.
static auto& g_environ_utf8 = *new std::unordered_map<std::string, char*>();
// Make sure that shadow UTF-8 environment variables are setup.
static void _ensure_env_setup() {
// If some name/value pairs exist, then we've already done the setup below.
if (g_environ_utf8.size() != 0) {
return;
}
if (_wenviron == nullptr) {
// If _wenviron is null, then -municode probably wasn't used. That
// linker flag will cause the entry point to setup _wenviron. It will
// also require an implementation of wmain() (which we provide above).
====> fatal("_wenviron is not set, did you link with -municode?");
}
Is there a file missing ( _municode trigger ?) to run properly in 64bit linux laptop and the wine configuration that has to do with the UTF-16 <-> UTF-8 thing ?
Strangely I renamed the adb.exe in the dir platform-tools from adb.exe to _adb.exe and when trying to compile install in B4A (connected with wifi - gives connected status on phone and B4A) to phone still gives the error as before. How is that possible, it should now give a missing file error, don't you think !
I've read in the forum that B4a-bridge does not use adb (??) why then this call to adb and error?
Is there a way to invoke from B4A (setting ) for B4A bridge to compile and debug and be sure it is not calling adb.exe, thus avoiding this error ?
Thanks for any suggestions.
dinge