makesis problem in 9.1 SDK's

I have noticed that makesis -d directory doesn't work anymore. The only 
paths that appear to work are relative paths. This happens in both the S60 
3rd edition sdk's and the UIQ 3 sdk. It is still possible to use relative 
paths, but this is a pain. Further, makesis -d is still advertised as 
working.

-- 
Sander van der Wal
www.mBrainSoftware.com 

Hi Sander

Thanks very much. Yes, this was noticed and a patch fed back into the
codelines in early March. UIQ have the fix but may not have released SDK
patch since then.

I'll try get the right version published and get back to you. Please email
me directly if I haven't got back toyou in a week.

Regards
H
"Sander van der Wal" <svdwal@mBrainSoftware.com> wrote in
message
news:zJCtLsanGHA.4968@UKCOL01WWEB01.symbian.intra...
> I have noticed that makesis -d directory doesn't work anymore. The only
> paths that appear to work are relative paths. This happens in both the S60
> 3rd edition sdk's and the UIQ 3 sdk. It is still possible to use relative
> paths, but this is a pain. Further, makesis -d is still advertised as
> working.
>
> -- 
> Sander van der Wal
> www.mBrainSoftware.com
>
>

Hamish Willee wrote:
> I'll try get the right version published.

Thanks for the file Hamish. It is now published at 
http://developer.uiq.com/devtools_other.html

br -d
-- 
David Mery <david.mery@uiq.com>, +44 7973 204 214
Editor - Developer program, Developer community team, UIQ Technology

Hamish Willee wrote:

>> I have noticed that makesis -d directory doesn't work anymore. The
only
>> paths that appear to work are relative paths. This happens in both the
S60
> Thanks very much. Yes, this was noticed and a patch fed back into the
> codelines in early March. UIQ have the fix but may not have released SDK
> patch since then.

I have now switched to using the new makesis file from 
developer.uiq.com, and it does indeed fix the "-d" switch, with one 
exception:

It seems that the icon definition for the SIS file (the "=" statement)

still does not take into account a given search path. I.e. if I have a 
line like this...

	="MySettings.mbm", "image/x-mbm", ""

the file MySettings.mbm is stilled searched for relative to the current 
directory only, rather than the "-d" path.

I am not sure if the package icon is even good for anything on the 
current platforms (I have never seen one appear on my S60 3rd Edition 
phones at least), but I at least the usage of paths should be consistent 
across all statements IMO.

ciao marcus

btw: A good extension would be the ability to specifiy multiple 
directories as a path, since generated files of different types are 
often spread out across several directories. I have even seen the places 
of some (namely resource files) change between SDK versions, at least 
prior to Symbian 9, and it would be nice if this could be isolated from 
he .pkg file.

My workaround so far has been to copy the output of "abld -w" into a 
single directory as part of my top-level build script, and then specify 

Hi Marcus
What if you have
"/MySettings.mbm", "image/x-mbm", ""
Regards
H

"Marcus Groeber" <marcus.groeber@nuance.com> wrote in message
news:606QAUazGHA.1380@UKCOL01WWEB01.symbian.intra...
> Hamish Willee wrote:
>
> >> I have noticed that makesis -d directory doesn't work anymore. The
only
> >> paths that appear to work are relative paths. This happens in both
the
S60
> > Thanks very much. Yes, this was noticed and a patch fed back into the
> > codelines in early March. UIQ have the fix but may not have released
SDK
> > patch since then.
>
> I have now switched to using the new makesis file from
> developer.uiq.com, and it does indeed fix the "-d" switch, with
one
> exception:
>
> It seems that the icon definition for the SIS file (the "="
statement)
> still does not take into account a given search path. I.e. if I have a
> line like this...
>
> ="MySettings.mbm", "image/x-mbm", ""
>
> the file MySettings.mbm is stilled searched for relative to the current
> directory only, rather than the "-d" path.
>
> I am not sure if the package icon is even good for anything on the
> current platforms (I have never seen one appear on my S60 3rd Edition
> phones at least), but I at least the usage of paths should be consistent
> across all statements IMO.
>
> ciao marcus
>
> btw: A good extension would be the ability to specifiy multiple
> directories as a path, since generated files of different types are
> often spread out across several directories. I have even seen the places
> of some (namely resource files) change between SDK versions, at least
> prior to Symbian 9, and it would be nice if this could be isolated from
> he .pkg file.
>
> My workaround so far has been to copy the output of "abld -w"
into a
> single directory as part of my top-level build script, and then specify
> that with "-d".