Revision history [back]

There seems to be something wrong with the SailfishOS SDK (first of all update never works, both VMs gets broken and unusable), but when you have made a re-installation of the SDK (first run the remove all components, then download the new version of the SDK and then manually install it), old projects will not work, the SDK should be able to update projects with default settings for build environment so that you can build and run the package in the emulator. (for me there ain't any options to start emulator or build machine for old project, only new ones which are created with the current SDK, starting the VMs manually will not make it possible to build anything, you end still with the "sailfishapp.h: No such file or directory".

A major improvement would be that the MerVM would be replaces by a native cross compiler environment, that way you get rid of half the issue at least. These issues don't seem to appear with Tizen SDK (I know it don't use qtcreator but it don't have a VM for build environment either). Now I seem to be forced to create a new project and start to migrate files from the old project and it becomes more and more files for each update of the SDK.

There seems to be something wrong with the SailfishOS SDK (first of all update never works, both VMs gets broken and unusable), but when you have made a re-installation of the SDK (first run the remove all components, then download the new version of the SDK and then manually install it), old projects will not work, the SDK should be able to update projects with default settings for build environment so that you can build and run the package in the emulator. (for me there ain't any options to start emulator or build machine for old project, only new ones which are created with the current SDK, starting the VMs manually will not make it possible to build anything, you end still with the "sailfishapp.h: No such file or directory".

A major improvement would be that the MerVM would be replaces by a native cross compiler environment, that way you get rid of half the issue at least. These issues don't seem to appear with Tizen SDK (I know it don't use qtcreator but it don't have a VM for build environment either). Now I seem to be forced to create a new project and start to migrate files from the old project and it becomes more and more files for each update of the SDK.

There seems to be something wrong with the SailfishOS SDK (first of all update never works, both VMs gets broken and unusable), but when you have made a re-installation of the SDK (first run the remove all components, then download the new version of the SDK and then manually install it), old projects will not work, the SDK should be able to update projects with default settings for build environment so that you can build and run the package in the emulator. (for me there ain't any options to start emulator or build machine for old project, only new ones which are created with the current SDK, starting the VMs manually will not make it possible to build anything, you end still with the "sailfishapp.h: No such file or directory".

A major improvement would be that the MerVM would be replaces by a native cross compiler environment, that way you get rid of half the issue at least. These issues don't seem to appear with Tizen SDK (I know it don't use qtcreator but it don't have a VM for build environment either). Now I seem to be forced to create a new project and start to migrate files from the old project and it becomes more and more files for each update of the SDK.

There seems to be something wrong with the SailfishOS SDK (first of all update never works, both VMs gets broken and unusable), but when you have made a re-installation of the SDK (first run the remove all components, then download the new version of the SDK and then manually install it), old projects will not work, the SDK should be able to update projects with default settings for build environment so that you can build and run the package in the emulator. (for me there ain't any options to start emulator or build machine for old project, only new ones which are created with the current SDK, starting the VMs manually will not make it possible to build anything, you end still with the "sailfishapp.h: No such file or directory".

A major improvement would be that the MerVM would be replaces by a native cross compiler environment, that way you get rid of half the issue at least. These issues don't seem to appear with Tizen SDK (I know it don't use qtcreator but it don't have a VM for build environment either). Now I seem to be forced to create a new project and start to migrate files from the old project and it becomes more and more files for each update of the SDK.

SDK4 failed to use SDK3 project

There seems to be something wrong with the SailfishOS SDK (first of all update never works, both VMs gets broken and unusable), but when you have made a re-installation of the SDK (first run the remove all components, then download the new version of the SDK and then manually install it), old projects will not work, the SDK should be able to update projects with default settings for build environment so that you can build and run the package in the emulator. (for me there ain't any options to start emulator or build machine for old project, only new ones which are created with the current SDK, starting the VMs manually will not make it possible to build anything, you end still with the "sailfishapp.h: No such file or directory".

A major improvement would be that the MerVM would be replaces by a native cross compiler environment, that way you get rid of half the issue at least. These issues don't seem to appear with Tizen SDK (I know it don't use qtcreator but it don't have a VM for build environment either). Now I seem to be forced to create a new project and start to migrate files from the old project and it becomes more and more files for each update of the SDK.

SDK4 failed to use SDK3 project