tag:blogger.com,1999:blog-7742435659113733626.post2735425977612730756..comments2023-06-16T06:34:15.956-06:00Comments on Nokia Carbide.c++ on Eclipse: Carbide 1.3 End GameKen Ryallhttp://www.blogger.com/profile/13632672249607934353noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-7742435659113733626.post-75259273662315278952008-02-26T09:23:00.000-06:002008-02-26T09:23:00.000-06:00OK - I know this isn't a support channel, but I fi...OK - I know this isn't a support channel, but I figure it can't hurt to ask - and this blog entry was clearly sympathetic to "unreproducible" bugs - so here goes.<BR/><BR/>The A/V or Firewall issue in my point 2 has been <A HREF="http://discussion.forum.nokia.com/forum/showthread.php?t=119227" REL="nofollow">reported on forum.nokia</A> by others. <I>(Yes, I am also "UncleOp".)</I><BR/><BR/>How can one work to resolve this, either with v1.2 or v1.3? There has been relative silence on forum.nokia regarding a solution to this particular issue.<BR/><BR/>As to no longer supporting W2K, is that an explicit non-support (i.e., will not permit installation) or is it an implicit non-support (Nokia will ignore bug reports)? If v1.3 doesn't help with the first issue, I'll be left high and dry.<BR/><BR/>Unless, of course, v1.3 will finally support development under Linux... (please?)Delhttps://www.blogger.com/profile/11375261998477364419noreply@blogger.comtag:blogger.com,1999:blog-7742435659113733626.post-66086366205059889502008-02-25T23:52:00.000-06:002008-02-25T23:52:00.000-06:00Carbide 1.3 does handle the build before debug ste...Carbide 1.3 does handle the build before debug step much better than 1.2, however we have dropped support for Win 2K and you still need to have your source and the SDK on the same drive. That said, I suggest you try 1.3 when it is released and contact our support team if you need help.Ken Ryallhttps://www.blogger.com/profile/13632672249607934353noreply@blogger.comtag:blogger.com,1999:blog-7742435659113733626.post-49845938107930612752008-02-25T16:40:00.000-06:002008-02-25T16:40:00.000-06:00I've been using v1.2 for a couple of months now to...I've been using v1.2 for a couple of months now to port a legacy project. I'm curious to know if v1.3 has addressed two particularly vexing problems I've had:<BR/><BR/>1) I have a large project; 37 static libraries (built as one library per directory). Because of problem #2 below, I have to build on an old Windows 2000 system, and if I press "Debug...", I have to wait a long time for the system to check over all 37 .mmp files' worth of source to see that I changed one line of code. Is there a way to say, "build this .mmp only", in either v1.2 or v1.3?<BR/><BR/>2) I have to run on the old system because the S60 emulator doesn't run with a WinXP-Pro system and the firewall and A/V settings enforced by my company. But since I have to keep all my tools on the same drive letter, I can't let the faster system do the compile in a seamless way. Will v1.3 allow the workspace to be located on a different drive letter from the base IDE, tools, and SDK install?Delhttps://www.blogger.com/profile/11375261998477364419noreply@blogger.com