<div dir="ltr">As I said in previous emails I cannot understand why we should use command line utilities to make our life difficult when there are so many and powerful IDEs. <div><br></div><div>Since the IDE with the SDK is QtCreator I am using it. If on the other hand you or someone else could provide guidelines on how I can setup eclipse IDE to use the appropriate compiler/linker and make that IDE work with jolla developer engine in combination with both emulator and actual device I would much appreciate.</div>
<div><br></div><div>For example I have one instance of eclipse IDE with different workspaces and depending on the workspace I open I am building for different mobile platform such as webOS, BlackBerry (PlayBook and BB10) and badaOS/TizenOS. That means all my games are source compatible and whenever I need to do something in a different way in one platform I use a wrapper class with common interface and different implementation having #if - #elseif - #endif brackets for each platform, for instance when accessing resources and reading/writing files since each platform has different privileges and access writes. I even managed to have my MAC with xCode IDE to use my sources and now use c/c++ instead of objective-c</div>
<div><br></div><div>It's a lot more easy to do step-by-step debugging from an IDE and display the contents of pointers, variables and STL containers and modify them at will, jump backwards or forwards in code to test it. As I see it an IDE is a lot more than just a simple editor for writing code, a good IDE with its utilities takes a way a lot of burden from you so that you can concentrate on the actual problem the design and development.</div>
<div><br></div><div>Check my blog at <a href="http://7cecdab4.blogspot.gr/">http://7cecdab4.blogspot.gr/</a> to see several games on different mobile platforms all source compatible all debugged in one platform for common (major part) of the code and all using a common IDE</div>
<div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On 17 April 2014 09:53, Andrey Kozhevnikov <span dir="ltr"><<a href="mailto:coderusinbox@gmail.com" target="_blank">coderusinbox@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
Why you using Qt creator then? use mb/mb2 in mer sdk.<br>
<br>
<div>17.04.2014 12:47, Iosif Hamlatzis
пишет:<br>
</div><div><div class="h5">
<blockquote type="cite">
<div dir="ltr">Good morning to all
<div><br>
</div>
<div>Just updated my SDK with big disaster. Now it doesn't build
or clean my project which used custom build/clean steps. </div>
<div><br>
</div>
<div>In my game I don't need nor want to use Qt so I used the
sample from <a href="https://github.com/sailfish-sdk/sdk-sdl-project-example" target="_blank">https://github.com/sailfish-sdk/sdk-sdl-project-example</a></div>
<div><br>
</div>
<div>Now I get a general message: "<b>Error while parsing file
C:/SailfishOS-workspace/harbour-farwest/<a href="http://harbour-farwest.pro" target="_blank">harbour-farwest.pro</a>.
Giving up.</b>"</div>
<div><br>
</div>
<div><br>
</div>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On 16 April 2014 14:21, Jarko Vihriala
<span dir="ltr"><<a href="mailto:jarko.vihriala@jolla.com" target="_blank">jarko.vihriala@jolla.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<div style="direction:ltr;font-size:10pt;font-family:Tahoma">Hello
all,<br>
<br>
We just discovered a serious issue related to using SDK
with KDE based Linux distros such as Fedora or KUbuntu.
Therefore we have removed the Linux installers from the
SailfishOS website. Please do not try to download Linux
installers or update your SailfishOS SDK if you are
using KDE Linux distro.<br>
<br>
We are now working to get the KDE issue solved, please
stay tuned. We will inform when SDK updates are again
available.<br>
<br>
thanks, Jarko<br>
<br>
<br>
<br>
<div style="font-size:16px;font-family:Times New Roman">
<hr>
<div style="direction:ltr"><font color="#000000" face="Tahoma"><b>From:</b> Jarko Vihriala<br>
<b>Sent:</b> Tuesday, April 15, 2014 9:36 PM<br>
<b>To:</b> Sailfish OS Developers<br>
<b>Subject:</b> SailfishOS SDK April update
available tomorrow.<br>
</font><br>
</div>
<div>
<div>
<div>
<div style="direction:ltr;font-size:10pt;font-family:Tahoma">Hello
again,<br>
<br>
Tomorrow (16 April) at 10:00 UTC we will
publish new installers, and package
repositories for our Sailfish OS SDK version
Alpha-1404-Qt5. Please note that links in this
email are updated at that time as well.<br>
<br>
We apologise for the long delay between the
SDK updates. We had to completely recreate our
SDK production environment before being able
to release an update. This took longer than
expected and is the main reason for the delay.<br>
<br>
If you already have an existing Alpha-Qt5 SDK
installed you should see the Updates Available
icon in Qt Creator. If you don't have a
previous SDK installation you can get the
latest installer from <a href="http://www.sailfishos.org" target="_blank">http://www.sailfishos.org</a>.
It is recommended to uninstall the old SDK and
download a new installer. <br>
<br>
SDK content has been updated to match Jolla
Release 1.0.5.16. Please see below for
detailed information of the changed items.<br>
<br>
A couple of things you should be aware of:<br>
- Like before, in this update the build
engine, emulator and targets are re-installed
so you will lose all changes you may have made
in those - however, if your application
packaging is done correctly, rebuilding your
projects should reinstall the packages you
have been using.<br>
- All customization done to SDK (adding new
package repositories, adding custom targets,
additional source paths) will be removed
during the installation process so make your
own backup of those before starting the
update.<br>
- If you import existing projects made with a
previous version of the Sailfish OS SDK, make
sure you select the correct kit in the project
configuration step. Both ARM and i486 kits are
available.<br>
- Windows users need to install VC10 runtime
from <a href="http://www.microsoft.com/en-us/download/confirmation.aspx?id=8328" target="_blank">http://www.microsoft.com/en-us/download/confirmation.aspx?id=8328</a>
or the Installer will ask for admin rights
during installation.<br>
- Package repository contents have been
updated and consequently using a previous SDK
version with these package repositories is not
supported.<br>
- For more information, please see the SDK
Alpha-Qt5 known issues list at: <a href="https://sailfishos.org/wiki/SDK_Alpha_Qt5_Known_Issues" target="_blank">https://sailfishos.org/wiki/SDK_Alpha_Qt5_Known_Issues</a>.<br>
- Oldest Mac OS X supported is now 10.8.5
(Mountain Lion). Other supported platforms can
be found from: <a href="https://sailfishos.org/alpha_qt5_sdk_release_notes.html" target="_blank">https://sailfishos.org/alpha_qt5_sdk_release_notes.html</a><br>
<br>
Here is a summary of changes:<br>
<br>
SDK IDE (Qt Creator)<br>
- Crash fixes on OS X<br>
- Yaml editor removed from Qt Creator and
yaml files are presented as plain text<br>
- Alternate projects folder can be changed
from Mer settings page<br>
- Better path handling for shared directories
in Windows<br>
- Updated Sailfish template project<br>
- Handle errors in project build/deploy phase
more gracefully<br>
- Debugging with GDB from Qt Creator works
with the Emulator and the Device<br>
- Tooltips are displayed for Virtual Machine
statuses<br>
- Add changelog to your RPM with a .changes
file<br>
<br>
SDK Control Center:<br>
- Improved Targets management page<br>
- Clean build targets are available for
download via the Targets page (pre-configured
targets)<br>
- Easily install/remove multiple packages
from a specific target<br>
- Updates page has a "Check for updates now"
button<br>
- Added Harbour tools page with RPM validator
tool<br>
<br>
Installer:<br>
- Better VirtualBox version checking. Lowest
version supported is v4.0<br>
- Install virtual machines using correct
VirtualBox version specific parameters<br>
- Handle empty alternate projects folder
setting<br>
- Install Sailfish template project as a
package making it easier to update<br>
- Display Sailfish logo on Mac installer<br>
- MerSDK no longer directly uses User's home
directory, but mounts it as
/home/mersdk/share/ inside the virtual machine<br>
- User's home directory is no longer polluted
with a .scratchbox2 folder<br>
- Shared mounts are mounted with correct
access rights<br>
- Default i486 target renamed to
SailfishOS-i486<br>
- Rework documentation packaging<br>
<br>
Emulator:<br>
- Applications can be removed from the
Emulator's home screen by long-clicking on the
application icon, just like it is done on the
phone.<br>
<br>
If you have any questions, you can either send
email to this mailing list: <a href="mailto:devel@lists.sailfishos.org" target="_blank">devel@lists.sailfishos.org</a>
or write it up in <a href="http://together.jolla.com" target="_blank">http://together.jolla.com</a>
and tag your issue with 'sdk'.<br>
<br>
Happy hacking, <br>
Jolla SDK Team.<br>
<br>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<br>
_______________________________________________<br>
SailfishOS.org Devel mailing list<br>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
SailfishOS.org Devel mailing list</pre>
</blockquote>
<br>
</div></div></div>
<br>_______________________________________________<br>
SailfishOS.org Devel mailing list<br></blockquote></div><br></div>