Results 1 to 4 of 4

Thread: "sencha app build" error on windows

  1. #1
    Ext JS Premium Member
    Join Date
    Jun 2010
    Posts
    11
    Vote Rating
    0
      0  

    Default "sencha app build" error on windows

    "sencha app build" error on windows


    Sencha Cmd 3.0.0.230
    Ext 4.1.1a
    Compass installed and added the path to the environment

    this is what I did:
    - created a new project with 'sencha generate myApp' -> OK
    - tried to build the app with
    'sencha build app myApp' ->


    ...
    [INFO ] -sass:
    [INFO ]
    [INFO ] [shellscript] "compass" is not recognized as an internal or external command,
    [INFO ]
    [INFO ] [shellscript]
    [INFO ]
    [INFO ] [shellscript] C:\...\myApp\resources\sass\default>compass compile --boring --force
    [INFO ]
    [INFO ] [shellscript]
    [INFO ]
    [ERROR]
    [ERROR] BUILD FAILED
    [ERROR] com.sencha.exceptions.BasicException: The following error occurred while executing this line:
    ...

    - compass is running fine from the command-line:
    I changed into 'C:\...\myApp\resources\sass\default'
    and ran the command 'compass compile --boring --force' -> OK, build was generated

    Any help to solve the build error?
    Is it possible to skip the compass-command ?
    Thanks

  2. #2
    Sencha User dongryphon's Avatar
    Join Date
    Jul 2009
    Location
    Kansas
    Posts
    1,740
    Vote Rating
    259
      0  

    Default

    You can disable compass compilation (see http://www.sencha.com/forum/showthre...l=1#post904896).

    That is odd that you can run compass from the console but the build script cannot. What version of Windows and Java do you have?
    Don Griffin

    "Use the source, Luke!"

  3. #3
    Ext JS Premium Member
    Join Date
    Jun 2010
    Posts
    11
    Vote Rating
    0
      0  

    Default

    I'm using Win7 and Java 1.7.0_05

  4. #4
    Sencha User dongryphon's Avatar
    Join Date
    Jul 2009
    Location
    Kansas
    Posts
    1,740
    Vote Rating
    259
      0  

    Default

    I am curious if your on a 64-bit Windows and if your JRE is 32-bit or 64-bit?

    This could be caused by trying to hop from 32-bit JRE to 64-bit compass or vise-verse. Just a guess though.
    Don Griffin

    "Use the source, Luke!"

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •