Re: An app is born and more about the future of SWI's development tools

On 08/19/2013 08:38 AM, Jochem Liem wrote:
> Hi,
> 
> The App crashes on startup on MacOSX 10.6.8. I tries to load
> '/usr/lib/libc++.1.dylib', but it does not exist.

:-(  I'll check the Qt docs.  I thought it said things would
run from 10.6 onwards.  Maybe it needs some flag.

	Thanks --- Jan

> 
> Best regards,
> Jochem
> 
> 
> 
> Process:         swipl-win [237]
> Path:            /Volumes/SWI-Prolog/SWI-Prolog.app/Contents/MacOS/swipl-win
> Identifier:      org.swi-prolog.swipl-win
> Version:         ??? (???)
> Code Type:       X86-64 (Native)
> Parent Process:  launchd [96]
> 
> Date/Time:       2013-08-19 09:34:00.640 +0300
> OS Version:      Mac OS X 10.6.8 (10K549)
> Report Version:  6
> 
> Interval Since Last Report:          713424 sec
> Crashes Since Last Report:           1
> Per-App Crashes Since Last Report:   1
> Anonymous UUID:                      D8DCF814-7276-499E-BED3-C20867560804
> 
> Exception Type:  EXC_BREAKPOINT (SIGTRAP)
> Exception Codes: 0x0000000000000002, 0x0000000000000000
> Crashed Thread:  0
> 
> Dyld Error Message:
>   Library not loaded: /usr/lib/libc++.1.dylib
>   Referenced from: /Volumes/SWI-Prolog/SWI-Prolog.app/Contents/MacOS/swipl-win
>   Reason: image not found
> 
> Binary Images:
>     0x7fff5fc00000 -     0x7fff5fc3be0f  dyld 132.1 (???)
> <29DECB19-0193-2575-D838-CF743F0400B2> /usr/lib/dyld
> 
> Model: MacBookPro5,5, BootROM MBP55.00AC.B03, 2 processors, Intel Core
> 2 Duo, 2.53 GHz, 2 GB, SMC 1.47f2
> Graphics: NVIDIA GeForce 9400M, NVIDIA GeForce 9400M, PCI, 256 MB
> Memory Module: global_name
> AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x8D),
> Broadcom BCM43xx 1.0 (5.10.131.42.4)
> Bluetooth: Version 2.4.5f3, 2 service, 19 devices, 1 incoming serial ports
> Network Service: AirPort, AirPort, en1
> Serial ATA Device: OCZ-VERTEX2, 223.57 GB
> Serial ATA Device: MATSHITADVD-R   UJ-868
> USB Device: Built-in iSight, 0x05ac  (Apple Inc.), 0x8507, 0x24400000 / 2
> USB Device: Internal Memory Card Reader, 0x05ac  (Apple Inc.), 0x8403,
> 0x26500000 / 2
> USB Device: BRCM2046 Hub, 0x0a5c  (Broadcom Corp.), 0x4500, 0x06100000 / 2
> USB Device: Bluetooth USB Host Controller, 0x05ac  (Apple Inc.),
> 0x8213, 0x06110000 / 5
> USB Device: Apple Internal Keyboard / Trackpad, 0x05ac  (Apple Inc.),
> 0x0237, 0x04600000 / 4
> USB Device: IR Receiver, 0x05ac  (Apple Inc.), 0x8242, 0x04500000 / 3
> USB Device: 2.4G Keyboard Mouse, 0x062a  (ProVision Technology, Inc.),
> 0x3286, 0x04100000 / 2
> 
> On Sun, Aug 18, 2013 at 12:17 AM, Jan Wielemaker <[email protected]> wrote:
>> Hi,
>>
>> After all the heat, it is time to test whether the `applification' of
>> SWI-Prolog will land in the Mac community.  The application is ready
>> for download from (this is a temporary place):
>>
>>         http://www.swi-prolog.org/download/MacOSX/SWI-Prolog-6.5.1.dmg
>>
>> Surely, it is still a bit rough.  It contains
>>
>>   - The main executable, swipl-win which is a graphical Qt-based
>>     application mainly provided by Carlo Capelli.
>>   - The usual commandline tools in Contents/MacOS
>>
>> It has been compiled on MacOS 10.7 (x64 Intel).  I have no clue on which
>> platforms it will run.  Getting one application that runs on a fair
>> range of Mac OS versions would be great ... Comments welcome.
>>
>>
>> ## About IDEs and versions.
>>
>> Some mails reached the list and me with worries about the future and
>> status of the various SWI-Prolog versions. I'll try clarify some points.
>>
>>   - First of all, SWI-Prolog itself is a *library*.  It is pretty
>>     unlikely anything will change to this concept.
>>
>>     - With a very small main program you have the usual application
>>       that communicates with the user through standard streams with
>>       or without fancy stuff such as (GNU-)readline.  See src/pl-main.c.
>>     - And, you can also talk to it using the C interface with many
>>       other interfaces on top of this (Java, C#, Python, Perl, ...).
>>
>>   - Second, there are XPCE based IDE tools: PceEmacs, gtrace, gxref,
>>     thread monitor, exception trapping interface, etc.  These form
>>     the `native' IDE and are accessible from any other IDE as long
>>     as there is XPCE accessible graphics (Windows or X11).  Whether
>>     these are there to stay is unclear.  XPCE is considered old and
>>     ugly.  X11 seems to be fading away, although I expect it to be
>>     available as an add-on on most platforms for quite a while.
>>
>>     The good news is that most of the logic behind these tools is
>>     written in Prolog and a lot is already separated from XPCE,
>>     mostly thanks the cooperation around PDT (see below).
>>
>>   - Then, on Windows, there is swipl-win.exe, a tiny Windows based
>>     app that merely adds some menus to a console.  It is widely
>>     critized for being slow, buggy, not Windows compliant, etc.
>>
>>   - Carlo wrote a replacement in Qt (a platform independent C++
>>     GUI toolkit).  This has now more or less the same functionality
>>     as swipl-win.exe.  It avoids most of the bugs of the old
>>     swipl-win.exe, but it is still in testing phase and quite
>>     likely comes with its own bugs.  The plan though is that this
>>     will be bundled with the binary releases for all platforms once
>>     it is considered stable enough.
>>
>>     It makes the system a bit easier accessible and allows for one
>>     guide for all platforms.
>>
>>   - Some people like running SWI-Prolog under (GNU-)Emacs.  That will
>>     work as long as people maintain a Prolog mode for (GNU-)Emacs, as
>>     this only relies on the commandline version.
>>
>>   - There is SWI-Prolog Editor by Gerhard Röhner.  I _think_ this
>>     encapsulates the old Windows swipl-win.exe.  That may require
>>     changes to deal with the Qt based one.  I'm planning to drop
>>     the old swipl-win.exe, simply because it is not portable and
>>     buggy.
>>
>>   - Last (but not least), there is PDT, the Eclipse based IDE from
>>     Guenter Kniesel and his group.  According to Paul Singleton,
>>     the availability of this tool is of considerable value for
>>     commercial users.  The Bonn group is quite determined to maintain
>>     this and we closely cooperate to get cleaner interfaces between
>>     Prolog and PDT.  This cooperation has proven to be productive
>>     for both ends.
>>
>> These are the things that exist. Then, by Torbjörn Lager, me and
>> probably some more people that will cooperate, web-based development
>> components start to become available. These tools can play many roles.
>> We can use them for web based applications, (cooperative) web-based
>> development tools, remote debugging of (embedded) Prolog systems or as
>> GUI IDE tools for Carlo's Qt based framework and I assume they can also
>> be used by PDT.
>>
>> One can surely state that it would be great if there was this one great
>> and fabulous development environment for all Prolog systems. I don't
>> think that will happen as long as we live in a free world ...  There
>> are simply too many preferences and systems differ so much that a
>> general IDE will be completely crippled.
>>
>>         Cheers --- Jan
>> _______________________________________________
>> SWI-Prolog mailing list
>> [email protected]
>> https://lists.iai.uni-bonn.de/mailman/listinfo.cgi/swi-prolog
> 
> 
> 
_______________________________________________
SWI-Prolog mailing list
[email protected]
https://lists.iai.uni-bonn.de/mailman/listinfo.cgi/swi-prolog