Compiling using Virtual Directory

[existdissolve]

This may be an incredibly stupid question, but it is possible to compile an app using an extjs library housed in a virtual directory? I have a virtual directory in my app which includes the library I want (currently 4.1.2a).

During development, this setup works just fine. All of the dependencies for my app files are found in the framework, and everything moves along without issues. However, when I compile, I get errors about dependency resolution - e.g., "Failed to resolve dependency Ext.container.Viewport for file..."

Is this possible to do, and if so, what am I missing?

NOTE: I haven't modified either of the .cfg files, and my compile looks like this:

sencha compile -classpath=ext\src,app page -in=index.html -out=build/index.html

EDIT:
I should also mention that:
* When I specify the full path to ext/src in classpath, the compile succeeds, but excludes any app classes
* When I put the library in my application root (no virtual directory), the compile succeeds and resolves all dependencies as expected

I appreciate any help anyone can offer. Thanks!

[existdissolve]

Okay, I believe I have it working. If anyone else is interested, here's the setup I have:

App Structure (Created via CMD)

/myapp
    /sencha
    /app
    /build
    /ext (virtual directorty)
    /resources 

App Sencha.cfg (Not modified)

app.name=MyApp 
app.framework=extapp.classpath=${app.dir}/app 

Workspace Sencha.cfg (Path changed)

workspace.build.dir=${workspace.dir}/build/${app.name}
ext.dir=ABSOLUTE_PATH_TO_SOURCE/extjs-4.1.3 

Compile

sencha compile -classpath=ext\src,app page -in=index.html -out=build/index.html 

[existdissolve]

For anyone interested, I did a fuller write-up on this here: http://existdissolve.com/2012/11/vir...4-development/

[Stormseeker]

For anyone interested, I did a fuller write-up on this here: http://existdissolve.com/2012/11/vir...4-development/

Unfortunately, it doesn't look this works with the full "sencha app build" command since the themeing portions such as compass/sass don't reference the sencha.cfg file but a hard-coded reference to the ext directory. Take a look at "youapp/resources/theme/default/theme.html".

It has a hard-coded reference to ext at the following location: src="../../../ext/ext-all.js".

Also the config.rb for the sass file is looking in the same place.

[dongryphon]

The path to the framework we etch in to the SASS world is computed at theme generation time... so it may work to generate a new theme after changing the configuration of your workspace.

[Stormseeker]

The path to the framework we etch in to the SASS world is computed at theme generation time... so it may work to generate a new theme after changing the configuration of your workspace.

Yup, that seemed to work perfectly. I just replaced the default theme.html file with the newly generated one and all is working. Thanks!