Re: [SailfishDevel] When does Jolla give us an API?
Hi, On 03.02.2014, at 16:58, David Greaves david.grea...@jolla.com wrote: On 03/02/14 15:29, Putze Sven wrote: Hi there, during Fosdem I spoke to some people about this, even to Carsten Munk from Jolla itself (not in the depth and detail of this mail, I must admit) and he suggested to write this in the mailing list, so those of Jolla who should be concerned have a chance to answer this question and I really would like to hear some official statements here. Did you manage to get to the round-table event? - we spent a fair bit of time talking about APIs there; we also openly discussed the issues we face. I know that the community people there wanted to continue the discussion. Yes, I got there but many people of the mailing list did not. From my point of view there is a discussion to be continued, one of the reasons I brought this topic up here. But IMHO it's not *just* a community thing, Jolla can't simply flinch and point at the community when it's getting unpleasant. Of course they can, but IMHO they shouldn't ;-) What does a developer need to write quality apps? An API and a documentation of such. So far there is a quite limited API available and therefore we don't see too many apps out there. How will you write a sophisticated app, if the API is not available or it is not allowed to use or is only known to those with Maemo/Meego history? A quick response: we support the Qt API and rather than developing our own proprietary one we're working hard to support the open one as it grows. The Qt documentation is extensive and superb :) As pointed out from others, it's not simply done with the Qt documentation. The Sailfish OS is built upon many libraries, frameworks and layers. But which one is to use? Is naming the building blocks enough? I am not writing this to run down other people or to make Jolla look bad. I am staying a pain in the ass because I truly believe that there is a gap and it needs to be filled. If you only want to address the geeky Linux approved developer with Meego background, this may be just enough to keep this eco system alive. Even if it does not seem this way right now, I *want* you to have success! If you want to attract mobile developers that are in the iOS, Android or even Windows Mobile universe right now, you need to offer them something more. Right now they are in a comfort zone. Besides that the Qt documentation is extensive and maybe extraordinary for an open source project, but it has much headroom for improvement^^. Using it in Sailfish Silica apps is less well documented but is improving (and honestly is mainly a tutorial issue for new developers - not an API docs issue). That depends on the definition of a new developer. If *new* means new to the platform then it's exactly the kind of developer and the problems they will have, that's what the whole topic is about. Try to see it from this perspective: I *am* new to the platform, hence not (yet) wearing rose-colored glassed. And maybe - just maybe - I (still) ask the right questions. BR. Sven When I write you, it's not so much you as in David, it's more like in Jolla ;-) signature.asc Description: Message signed with OpenPGP using GPGMail ___ SailfishOS.org Devel mailing list
[SailfishDevel] When does Jolla give us an API?
Hi there, during Fosdem I spoke to some people about this, even to Carsten Munk from Jolla itself (not in the depth and detail of this mail, I must admit) and he suggested to write this in the mailing list, so those of Jolla who should be concerned have a chance to answer this question and I really would like to hear some official statements here. Let's just assume the business model of Jolla is selling phones and/or operating systems (that is not meant as a joke neither as rant, I simply don't know their business model and they don't need to tell me, to make that clear - referring to http://stezz.blogspot.de/2013/10/jolla-community-and-innovation.html here). But for the sake of convenience I further presume they want to sell phones. Doesn't seem too absurd to me. Jolla must sell phones to pay their bills in the end. More sales = easier life (I am simplifying here). What brings more sales? A phone that is somehow attractive to the user. So far Jolla lived from the geek factor and there is nothing wrong about that but geeks alone are IMHO not enough to pay future bills. What may be attractive to Mr. and Mrs. Average? A phone that has a somehow *sexy* image? Maybe. A phone that comes together with an attractive eco system (and I chose the words eco system here with thought)? Yes! What makes an eco system attractive? Many quality *native* apps. *Native* is the keyword here, because many and sometimes quality apps can be found on any other platform ou there. Only *native* apps come with the user interface that distinguish a Jolla phone from other phones (from the user perspective). What does a developer need to write quality apps? An API and a documentation of such. So far there is a quite limited API available and therefore we don't see too many apps out there. How will you write a sophisticated app, if the API is not available or it is not allowed to use or is only known to those with Maemo/Meego history? Maybe there are not so many developers interested in SailfishOS? Fosdem clearly showed a lot of interest! What will draw the attention of a developer to this eco system if not a way to make money and/or easy development? Making money out of the harbour store is not possible (yet), so it could only be the latter (ignoring the geek factor here). So please, please, give us APIs and documentation. Does the API change? So what? Life is change and a changing API is a zillion times better to have than none at all. Yes, there is some level of frustration in these words here, but I hope they don't come across as a rant. They are meant as constructive criticism and maybe as a a broad hint 8) BR. Sven signature.asc Description: Message signed with OpenPGP using GPGMail ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] Harbour compliant way to read contacts
Hi, I am just wondering why there was the idea hey, let's do some bondage and use the Google API (or Facebook or...) instead of using CardDav and CalDav from the beginning. Shouldn't that have been the natural choice for an more or less open phone? Nevertheless I will be happy when the alternatives arrive. BR. Sven signature.asc Description: Message signed with OpenPGP using GPGMail ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] Sharing a common OfflineStorage DB between multiple Sailfish apps.
Hi,
What are the pros and cons of using QStandardPaths as opposed to XDG
Environmental Variables?
If you look into the unix implementation of the class QStandardPaths, you find
something like
QString QStandardPaths::writableLocation(StandardLocation type)
{
switch (type) {
case HomeLocation:
return QDir::homePath();
case TempLocation:
return QDir::tempPath();
case CacheLocation:
case GenericCacheLocation:
{
// http://standards.freedesktop.org/basedir-spec/basedir-spec-0.6.html
QString xdgCacheHome = QFile::decodeName(qgetenv(XDG_CACHE_HOME));
if (isTestModeEnabled())
xdgCacheHome = QDir::homePath() + QLatin1String(/.qttest/cache);
if (xdgCacheHome.isEmpty())
xdgCacheHome = QDir::homePath() + QLatin1String(/.cache);
if (type == QStandardPaths::CacheLocation)
appendOrganizationAndApp(xdgCacheHome);
return xdgCacheHome;
}
case DataLocation:
case GenericDataLocation:
{
QString xdgDataHome = QFile::decodeName(qgetenv(XDG_DATA_HOME));
if (isTestModeEnabled())
xdgDataHome = QDir::homePath() + QLatin1String(/.qttest/share);
if (xdgDataHome.isEmpty())
xdgDataHome = QDir::homePath() + QLatin1String(/.local/share);
if (type == QStandardPaths::DataLocation)
appendOrganizationAndApp(xdgDataHome);
return xdgDataHome;
}
case ConfigLocation:
{
// http://standards.freedesktop.org/basedir-spec/latest/
QString xdgConfigHome = QFile::decodeName(qgetenv(XDG_CONFIG_HOME));
if (isTestModeEnabled())
xdgConfigHome = QDir::homePath() + QLatin1String(/.qttest/config);
if (xdgConfigHome.isEmpty())
xdgConfigHome = QDir::homePath() + QLatin1String(/.config);
return xdgConfigHome;
}
So using QStandardPaths is
* convenience and brings you
* OS independance, because they (Qt) tend to choose the right position.
BR.
Sven
signature.asc
Description: Message signed with OpenPGP using GPGMail
___
SailfishOS.org Devel mailing list
[SailfishDevel] SDK / Deploy / Problem with subprojects
Hi there, let's assume I've got an umbrella project file myApp.pro which is in some BaseDir: TEMPLATE = subdirs SUBDIRS = myAppLogic myAppSFOS CONFIG += ordered myAppSFOS.depends = myAppLogic There are 2 subprojects, first there is myAppLogic which builds a library, second is myAppSFOS which builds the application for SailfishOS/Jolla device. myAppSFOS.pro has all the needed information about the library, so it should be put in the right place if one calls 'make install'. So far so good. All compiles well and then comes the deploy part. Regardless of the deployment method I get the following error message: Fatal: No spec file found in 'BaseDir/rpm/' and couldn't make one from a yaml Well, yes that's true - no .yaml file there. It should look at BaseDir/myAppSFOS/rpm/ Is this a bug in the SDK? (as in we are using a hardcoded path here) Am I doing it wrong? Can I somehow tell the deploy process where to look? BR. Sven P.S.: it's somehow related to the topics [SailfishDevel] adding libraries to sailfish app. and ''Project tries to use spec file from another project but I decided not to hijack them. ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] Qt Creator Yaml file editor loses new entries
Hi, IMHO the .yaml file is (partly) rewritten if something changes in your .pro file, could this be your problem here? BR. Sven On 29.12.2013, at 17:48, christopher.l...@thurweb.ch wrote: Hi All If add a new dependency to the a projects .yaml file via the QtCreator yaml file editor, then immediately hit cmd S to save the changes, then more often than not the new entry vanishes, and i have to repeat the process. So far I have not established exactly what pattern of circumstances is required for this to happen / not happen (e.g. focus still on new entry), and I now always double check after every save. I am running the very latest SDK on OSX. Chris ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] Check for OS in .PRO file
Thanks,
Thomas' hint of avoiding the conditionals convinced me somehow :-)
BR.
Sven
On 04.01.2014, at 12:15, David Greaves david.grea...@jolla.com wrote:
Just for the record this will fail to build on the Community OBS or even in a
Mer Platform SDK using a SailfishOS target.
Thomas and Timur's suggestions would work.
David
On 04/01/14 10:42, Putze Sven wrote:
Hi,
I should read my mails more often 8) Just figured out
win32|macx{
SDKHOSTNAME=unknown
}
linux-g++{
SDKHOSTNAME=$$system(hostname)
}
contains(SDKHOSTNAME , SailfishSDK){
message(Heureka! Running on the MerSDK VM)
}
else{
message(running somewhere else)
}
But I will also think about what you guys wrote, thank you!
BR.
Sven
On 02.01.2014, at 20:25, Sven Putze sailfish...@hardcodes.de wrote:
Hi there,
first of all a happy new year to everyone! I had some time offline this
morning, so here comes a bunch of emails...
There are ways to check for the OS in QtCreator .PRO files, e.g. like
unix:symbian{ # do stuff}
unix:maemo5{ # do stuff}
macx{ # do stuff}
win32{ # do stuff}
Is there a way to check (or control to be more precise) that some
directives are only used when compiling on the MerSDL VM?
Just checking for the presence of sailfishapp does not work, because that
is defined for any OS.
BR.
Sven
___
SailfishOS.org Devel mailing list
___
SailfishOS.org Devel mailing list
___
SailfishOS.org Devel mailing list
[SailfishDevel] How to use QtTest?
Hi there, I am still in the process of how to organize projects in such a way that I want to make sure that they don't turn out as a maintenance nightmare and I can add other platforms in future. One topic of this is building the business logic as a library and create a test project for it. So far so good. Now I have tried to use QtTest and got an underlined error using #include QtTest in a header file. The corresponding CONFIG += qtestlib in the .PRO file leads to an unknown module(s) in QT error. Ok, the module is not part of the SDK, just install it in the Mer SDM virtual machine. But there is a module called qt5test installed, yet missing any header files. There is a qt5test-devel package. That brings header files but sounds more like I want to develop inside a qt library. Right now I don't see the wood for the trees, can someone show me a direction? :-) Thanks, BR. Sven P.S.: Writing separate business logic and tests for it seems to be interesting in general: why would I want to run it on the phone (emulator) the whole time? ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] How to use QtTest?
in a header file. The corresponding CONFIG += qtestlib Actually it is CONFIG += testlib but documented as qtestlib in one of the help files. But the problem remains the same. BR. Sven ___ SailfishOS.org Devel mailing list
[SailfishDevel] Request for modern C++ compiler in the SailfishOS SDK
Hi there, yes the subject is quite a bit provocative :-) When I get it right there is a gcc4.6.4 on the MerSDK virtual machine. An up-to-date version of gcc should be something around 4.8. Usually I am not part of the I must always have the latest version race but with reference to compilers this would be *really* nice to have. Just think of full C++11 support. And as you just mentioned it(*), are there any plans regarding clang as compiler? This thingy produces far better error messages than gcc. BR. Sven P.S.: this is not meant as a rant! (*) I had a clown for breakfast, sorry. ___ SailfishOS.org Devel mailing list
[SailfishDevel] Remote Xterm/Wayland session possible?
Hi all, would it be possible to open a (SSH tunneled) Xterm or Wayland session with the phone? Is there enough technology in the Wayland stack on the phone? Usecase could be presentation on a beamer, recording of what's happening on the phone. How did the Jolla guys make their remote presentations? USB? Thanks, BR. Sven ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] configure mail accounts via command line
On 25.12.2013, at 18:49, Andrey Kozhevnikov coderusin...@gmail.com wrote: what profit of using long crypted password if you can't remember it or just type, if you keeping your long and crypted password in some text file and pasting it every time you need to reset your mail account? My passwords are not in a plain text file, they are stored in a crypted KeePass file. Someone is creating an app for Jolla, so everything will be fine in future. The profit is of course security: I use different logon credentials for each and every account (not only emails). It's more about not re-using passwords for other accounts, the human brain is quite limited here ;-) And yes, this kind of security (or call it paranoia) comes at a price: inconvenience. BR. Sven P.S. Push2Sail came here to rescue, everything works fine now. ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] Remote Xterm/Wayland session possible?
Is there a VNC server available? I remember someone asking that as a feature. On 27.12.2013, at 11:43, Andrey Kozhevnikov coderusin...@gmail.com wrote: VNC? On 27.12.2013 16:40, Putze Sven wrote: Hi all, would it be possible to open a (SSH tunneled) Xterm or Wayland session with the phone? Is there enough technology in the Wayland stack on the phone? Usecase could be presentation on a beamer, recording of what's happening on the phone. How did the Jolla guys make their remote presentations? USB? ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] Developing with SailfishOS - a short introduction
Hi all, just a little update. A downloadable pdf version can now be found at http://hardcodes.de/SailfishOS/Developing-with-SailfishOS.pdf. It is still far from complete but grows :-) I went from thinking about moving to another markup language to I will move. But I am still thinking about which one?. If you ask for a gut reaction, I would answer MultiMarkDown. Still not sure... Have a nice weekend! BR. Sven ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] Sharing version number (and other constants?) between .yaml/spec, .pro and .cpp/.qml
Hi, I've used something like VERSION = 0.1.0 HC_GITHASH = $$system(git show HEAD|grep ^commit|cut -c 8-) # c style DEFINEs to access the git hash and program version DEFINES += HC_PROGRAMVERSION=\\\$$VERSION\\\ DEFINES += HC_GITHASH=\\\$$HC_GITHASH\\\ in the .PRO file. This provides access in the .PRO file itself and in any .h or .cpp file. From there should be a way to .qml (via Q_PROPERTY). Not sure about the .yaml file. BR. Sven On 07.12.2013, at 00:26, Artem Marchenko artem.marche...@gmail.com wrote: P.S. Oh well, super ideal version would pull tag from git into both .pro and .yaml, but I guess that is impossible without the custom scripts. On Sat, Dec 7, 2013 at 1:25 AM, Artem Marchenko artem.marche...@gmail.com wrote: Just what I was looking for. Thanks, Robin! Cheers, Artem. On Sat, Dec 7, 2013 at 12:50 AM, Robin Burchell robin.burch...@jolla.com wrote: https://github.com/nemomobile/mlite/blob/master/rpm/mlite-qt5.yaml#L20 gives you https://github.com/nemomobile/mlite/blob/master/rpm/mlite-qt5.spec#L60 if you want to go all out gung-ho with automation, you can also do something like https://github.com/nemomobile/mlite/blob/master/src/src.pro#L3 in your project file for local builds. On 06 Dec 2013, at 23:45, Artem Marchenko artem.marche...@gmail.com wrote: Hi All Does anybody know a way to share constants between .yaml and any other project file (preferably .pro, but any other way would do as well)? I sort of got tired to duplicate version numbers in .yaml and app's about dialog :) Writing app description in one place only would've been good too. Best regards, Artem. -- Artem Marchenko http://agilesoftwaredevelopment.com http://twitter.com/AgileArtem ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list -- Artem Marchenko http://agilesoftwaredevelopment.com http://twitter.com/AgileArtem -- Artem Marchenko http://agilesoftwaredevelopment.com http://twitter.com/AgileArtem ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] The missing HelloWorld. Wizard included
Hi, one thing I am trying to wrap my head around is the usage of a project for different devices/operating systems (why? because a living ecosystem needs to attract more developers and those coming from other platforms will come if they already use Qt or see a chance in switching to Qt but they sure don't want a maintenance nightmare). IMHO something like the rpm folder should go at least one directory level down, so one could differentiate between the brands or operating systems at top level. But so far any tests with rpm in another level broke apart. I am not sure if something is hardcoded here or if I simply don't know where to look? In such an attempt I would rename the folder src to sailfishos or something similar. What's your thoughts about that? BR. Sven On 30.11.2013, at 19:06, Artem Marchenko artem.marche...@gmail.com wrote: Hi All *Short version* Go check this out and contribute corrections - https://github.com/amarchen/helloworld-pro-sailfish *Long version* Just an app templates make my heart cry. Changing them to the proper structure is pain every time you go beyond just a helloworld. So I created a Helloworld Pro for Sailfish. Something that has minimal UI, but proper project structure and a couple of UI and non UI QML tests (includes src, test folders, multipackage .yaml/spec, proper 86x86 icon, etc) and passes harbour acceptance criteria (pending for now). And then I added a wizard script that renames everything to whatever project name you like to help you get started with MyCoolApp instead of helloworld-pro-sailfish Wizard is a bash script validated on Mac only, because that's the platform I use. Similar scripts for Windows and other corrections/improvements (e.g. adding simple app cover) are very welcome via pull requests. You will find the project at https://github.com/amarchen/helloworld-pro-sailfish If you want to do more with QML testing that I greatly encourage, this old presentation is still valid - www.slideshare.net/AgileArtem/test-drivingqml-12941898 Enjoy! Cheers, Artem. -- Artem Marchenko http://agilesoftwaredevelopment.com http://twitter.com/AgileArtem ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list
[SailfishDevel] qmake / Makefile - rules missing
Hi there, after I changed the structure inside of a test project, some of the rules in the resulting Makefile are missing. The structure is now as follows: TestSailfishOS/ ├── Makefile ├── TestSailfishOS ├── TestSailfishOS.pro ├── TestSailfishOS.pro.user ├── moc │ └── moc_qbusinesslogic.cpp ├── model │ ├── model.pri │ ├── qt │ │ ├── qbusinesslogic.cpp │ │ └── qbusinesslogic.h │ └── std │ ├── businesslogic.cpp │ └── businesslogic.h ├── obj │ ├── TestSailfishOS.o │ ├── businesslogic.o │ ├── moc_qbusinesslogic.o │ └── qbusinesslogic.o └── sailfishos ├── TestSailfishOS.cpp ├── TestSailfishOS.desktop ├── TestSailfishOS.png ├── qml │ ├── TestSailfishOS.qml │ ├── cover │ │ └── CoverPage.qml │ └── pages │ ├── FirstPage.qml │ └── SecondPage.qml ├── rpm │ └── TestSailfishOS.yaml └── sailfishos.pri The sailsihos/sailfishos.pri file is a variation of the standard template, just edited with the new path: # The name of your app. # NOTICE: name defined in TARGET has a corresponding QML filename. # If name defined in TARGET is changed, following needs to be # done to match new name: # - corresponding QML filename must be changed # - desktop icon filename must be changed # - desktop filename must be changed # - icon definition filename in desktop file must be changed CONFIG += sailfishapp SOURCES += sailfishos/TestSailfishOS.cpp OTHER_FILES += sailfishos/qml/TestSailfishOS.qml \ sailfishos/qml/cover/CoverPage.qml \ sailfishos/qml/pages/FirstPage.qml \ sailfishos/qml/pages/SecondPage.qml \ sailfishos/rpm/TestSailfishOS.spec \ sailfishos/rpm/TestSailfishOS.yaml \ sailfishos/TestSailfishOS.desktop Compiling works just fine, the moc file, *.o files and finally the binary are built. But there are missing some rules in the Makefile, which are quite essential for deploying and testing :-) These are missing: install_qml: first FORCE @test -d $(INSTALL_ROOT)/usr/share/TestSailfishOS || mkdir -p $(INSTALL_ROOT)/usr/share/TestSailfishOS -$(INSTALL_DIR) /home/mersdk/QtProjects/TestSailfishOS/qml $(INSTALL_ROOT)/usr/share/TestSailfishOS/ uninstall_qml: FORCE -$(DEL_FILE) -r $(INSTALL_ROOT)/usr/share/TestSailfishOS/qml -$(DEL_DIR) $(INSTALL_ROOT)/usr/share/TestSailfishOS/ install_desktop: first FORCE @test -d $(INSTALL_ROOT)/usr/share/applications || mkdir -p $(INSTALL_ROOT)/usr/share/applications -$(INSTALL_PROGRAM) /home/mersdk/QtProjects/TestSailfishOS/TestSailfishOS.desktop $(INSTALL_ROOT)/usr/share/applications/ uninstall_desktop: FORCE -$(DEL_FILE) -r $(INSTALL_ROOT)/usr/share/applications/TestSailfishOS.desktop -$(DEL_DIR) $(INSTALL_ROOT)/usr/share/applications/ install_icon: first FORCE @test -d $(INSTALL_ROOT)/usr/share/icons/hicolor/90x90/apps || mkdir -p $(INSTALL_ROOT)/usr/share/icons/hicolor/90x90/apps -$(INSTALL_PROGRAM) /home/mersdk/QtProjects/TestSailfishOS/TestSailfishOS.png $(INSTALL_ROOT)/usr/share/icons/hicolor/90x90/apps/ uninstall_icon: FORCE -$(DEL_FILE) -r $(INSTALL_ROOT)/usr/share/icons/hicolor/90x90/apps/TestSailfishOS.png -$(DEL_DIR) $(INSTALL_ROOT)/usr/share/icons/hicolor/90x90/apps/ So obviously qmake has a problem when leaving the expected path(s). Is this expected behavior? Is this a bug? Or must I now provide some extra settings in the sailfishos.pri file so that the rules in the Makefile are generated again? Thanks, BR. Sven ___ SailfishOS.org Devel mailing list
[SailfishDevel] http://releases.sailfishos.org/sdk/ --403 Forbidden
Hi, if I try to access http://releases.sailfishos.org/sdk/ which is linked from https://sailfishos.org/develop-overview-article.html I get 403 Forbidden. This might need a fix. BR. Sven ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] Third party modules / header files
Hi Christopher, http://flyingsheeponsailfish.blogspot.ch/2013/11/deploying-additional-packages-to.html Thanks for the read. So I am not so wrong at all :-) You should not need to map any additional drives for Qt Creator to find headers, the SDK VM already has shared folders that access you home drive (within which you have to install the Sailfish SDK). If my understanding of the official documentation is right, then the home folder of my development machine (where QtCreator runs) is shared with the VM. This way the compiler can access the source. But I want the other way around. Re-using header files already there on the SDK machine (the headless one). Is there a drive mapped into my home folder? And if yes, where? One point additional point discussed in many mails over the past few weeks is what / where can you install shared libraries to make your app compliant with the rules of the Jolla Harbour app store. My (shaky) understanding is that while technically you can use the Yaml / spec file to automatically install additional packages, for the app store you will have to bundle these with your app (i.e. not shared). Hm, so far I thought that this is true for everything that is _not_ available as RPM package in the NEMO repository. BR. Sven mfg Chris Zitat von Putze Sven sailfish...@hardcodes.de: Hi there, For some time now I am wondering what the best practice would be for using third party components. First off all I want to sketch my understanding so far: # I can use any RPM package that is available via zypper on the emulator AKA The SailfishOS Emulator. SSH in that thingy and install the files. That way the package is there, where it is needed and used in the end. # The same package plus header files are installed in the Mer build engine for cross compilation, so the compiler and linker can find/use them during compilation/linking time (and packaging time later on) Development is done on the QtCreator integrated development environment plus some plugins for the communication with the virtual machines (and later on the physical device). This is the only platform dependent piece of software since the rest is done in VMs. So far so good, now the washy part. # For developing convenience it would be nice if the editor in QtCreator knew about the header files that are part of the earlier mentioned packages. What's the best practice here? Do you guys mount a drive from the Mer build engine for cross compilation to simply re-use those header files for the QtCreator? Do you copy them over to a local path? Am I on the wrong path? ;-) # Finally there must be a way to tell the build system that there is a dependency to an existing RPM package. I assume that is somehow done in the .YAML file in the Requires section. Do I simply add the name of the package here? If that has been asked and answered before just point me to the appropriate resource, that I have googled it wrong. Best regards Sven ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] SDK and Harbour news
- Shared libraries · You can ship your own private copies of shared libraries that you link against in /usr/share/name of your app/, you are not allowed to install shared libraries anywhere else. Hi, do I get it right that for each and every App there will be a directory in the form /usr/share/mydomain.mygreatcompany.nameofmyapp which is private and for App access only? IMHO you could/should create a directory standard which should be followed inside this folder. E.g. like the bundle folders in the Apple universe. Best. Sven ___ SailfishOS.org Devel mailing list
