On 01/10/2013 01:58 PM, Martin Schreiber wrote:
>>
>> I don't understand.
>>
>> I can separate the compiled units from the source
>>
>> But
>>
>> Do I need to make changes in the "Settings -> Configure MSEide"?
>>
> Yes. ${MSELIBDIR} should point to the root of the unit directory tree.
>
>> Do I need to make changes in the "Project -> Options" directories for
>> U/I/L/O?
>>
> No. But the project templates should be changed to use ${MSEDIR}\lib\common
> instead of ${MSELIBDIR} in debugger source directories (done in git master
> 626a288035e554c0b4fa9a7fa25546830848e76a).
>
Well, this does not seem to be working out too well.
After splitting up the source and units I got the following error on my
first test:
Recompiling msearrayutils, checksum changed for msetypes.
And then it cannot write to the /usr/lib/mseide-msegui/.. folder as it
is owned by root.
So if this can happen then I don't think this approach will work.
I am going to install into the user's home directory and see how that works.
If someone is installing mseide-msegui then likely they will be doing
the compiling.
If we get to a situation where multiple users are compiling then I will
try a different approach. But for now it will be in the user's home
directory.
Should I make it a hidden or visible folder? Any other thoughts /
suggestions / objections?
Patrick
------------------------------------------------------------------------------
Master HTML5, CSS3, ASP.NET, MVC, AJAX, Knockout.js, Web API and
much more. Get web development skills now with LearnDevNow -
350+ hours of step-by-step video tutorials by Microsoft MVPs and experts.
SALE $99.99 this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122812
_______________________________________________
mseide-msegui-talk mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
