Only for tizen case, we should use at least one argments.
But if application created by dotnet launcher, It could be nullptr.
Other platform (like ubuntu / windows / etc..) don't need to add
dummy Arguments. So here, we try to attach some dummy arguments
only for tizen platform case.
Change-Id: Ib02a181e8579966ae2e9600bb27eecd040032c1d
Signed-off-by: Eunki, Hong <eunkiki.hong@samsung.com>
+// Note : tizen appfw don't consider zero-arguments case.
+// If framework argc & argv is nullptr, We should add at least one argv.
+const int gTizenDummyArgc = 1;
+const char* gTizenDummyArgv[1] = {"dali-tizen-app"};
+
} // anonymous namespace
namespace AppCore
} // anonymous namespace
namespace AppCore
callback.fini = ComponentAppFinish;
return component_based_app_base_main(*mFramework->mArgc, *mFramework->mArgv, &callback, mFramework);
callback.fini = ComponentAppFinish;
return component_based_app_base_main(*mFramework->mArgc, *mFramework->mArgv, &callback, mFramework);
}
static void* ComponentAppCreate(void* data)
}
static void* ComponentAppCreate(void* data)
mAbortHandler(MakeCallback(this, &Framework::AbortCallback)),
mImpl(NULL)
{
mAbortHandler(MakeCallback(this, &Framework::AbortCallback)),
mImpl(NULL)
{
+ if(mArgc == nullptr || mArgv == nullptr)
+ {
+ mArgc = const_cast<int*>(&gTizenDummyArgc);
+ mArgv = const_cast<char***>(reinterpret_cast<const char***>(&gTizenDummyArgv));
+ }
+
bool featureFlag = true;
system_info_get_platform_bool("tizen.org/feature/opengles.version.2_0", &featureFlag);
bool featureFlag = true;
system_info_get_platform_bool("tizen.org/feature/opengles.version.2_0", &featureFlag);