Changeset 15503


Ignore:
Timestamp:
Nov 23, 2012, 7:16:21 AM (7 years ago)
Author:
gb
Message:

Don't (briefly) start the event loop when building the standalone Cocoa
IDE (via (REQUIRE "COCOA-APPLICATION")), because:

  • there have been some problems with doing so in the past (e.g., Cocoa libraries trying to parse CCL command-line args.)
  • this may be related to a problem we're seeing in a project for a customer.
  • it's hard to think of a good reason to do so.

cocoa-ide/cocoa.lisp: call (GUI::START-COCOA-IDE) after everything's loaded.

cocoa-ide/start.iisp: in TOPEVEL-FUNCTION on COCOA-IDE, ensure that the

initial thread is of class APPKIT-PROCESS.

Don't wait for the semaphore in BUILD-IDE.
Don't call START-COCOA-IDE when this file is loaded.

Location:
trunk/source/cocoa-ide
Files:
2 edited

Legend:

Unmodified
Added
Removed
  • trunk/source/cocoa-ide/cocoa.lisp

    r15350 r15503  
    2121(load "ccl:cocoa-ide;defsystem.lisp")
    2222(load-ide *cocoa-ide-force-compile*)
     23(gui::start-cocoa-ide)
  • trunk/source/cocoa-ide/start.lisp

    r15365 r15503  
    9595    (#_ _exit -1))
    9696  (setq *standalone-cocoa-ide* t)
     97  (change-class ccl::*current-process* 'appkit-process)
    9798  (with-slots  (have-interactive-terminal-io) ccl::*current-process*
    9899    (when (and (eql (nth-value 4 (ccl::%stat "/dev/null"))
     
    119120
    120121  ;; Wait until we're sure that the Cocoa event loop has started.
    121   (wait-on-semaphore *cocoa-ide-finished-launching*)
     122  ;; (wait-on-semaphore *cocoa-ide-finished-launching*)
    122123
    123124  #-cocotron                            ;needs conditionalization
     
    280281
    281282
    282 (start-cocoa-ide)
     283;;(start-cocoa-ide)
Note: See TracChangeset for help on using the changeset viewer.