Viktor Szakáts wrote:
>
> It's only necessary if you want to avoid repeating
> the same long path a lot of times and this long path is
> not devisable from any root paths. For such purpose,
> you can use macros, like you say, and this is supported
> also by hbmk2 ('{MYPATH}\source.prg' and '-env:MYPATH=C:\dev_sources\').
>
Perfect. This is exactly what meta-data concept was all about.
Now the issue is how to fetch these variables from the user?
Because these are needed to be known before visual interaction
starts for fetching/including/removing sources in/from projects.
One idea could be
{hbMK2-env}MYPATH=C:\dev_sources\
{hbMK2-env}MYPATH_1=C:\dev_sources\common\
{hbMK2-env}MYPATHVOUCH=C:\dev_sources\vouch\
placeholder in hbide.env
another ?
> Anyway I don't like such solution, it's much simpler
> and self-contained if you create an .hbm file with
> list of files in your C:\dev_sources\this\that\ folder,
> named C:\dev_sources\this\that\filelist.hbm, and simply
> refer to this file using hbmk2 option:
> 'C:\dev_sources\this\that\filelist.hbm'
> or if you don't like .hbm extension, you can change it
> to anything and use: '@C:\dev_sources\this\that\filelist.ext'
> You can embed this option into your .hbp file.
> (Even the parser I wrote for hbide can be extended
> to support such embedding (see my notes in comments),
> but I stopped investing time into this.)
>
> The best solution tough is if you simply store you
> .hbp (or .hbi) file inside C:\dev_source\...\myproject.hbi,
> open it, and voila, it will find all the source files,
> without any extra trick.
>
Yes, this is the simplest one. And hbMK2 will receive
sources in this format only. The point of discussion is
how to retain path structures in visual concept.
> I don't know your workflow, but if you like to store
> you sources and the make files that belong to them in
> different places, detached from each other, you can
> stick to macros.
>
I did not know that concept of macros exists in hbMK2.
that is why I devised meta-data. I will finetune hbIDE to take
advantage of it. Bust as I said we need a placeholder
to know these values beforehand.
-----
enjoy hbIDEing...
Pritpal Bedi
_a_student_of_software_analysis_&_design_
--
View this message in context:
http://n2.nabble.com/hbide-pathProc-Merging-Paths-Clarification-tp4505657p4509879.html
Sent from the harbour-devel mailing list archive at Nabble.com.
_______________________________________________
Harbour mailing list (attachment size limit: 40KB)
[email protected]
http://lists.harbour-project.org/mailman/listinfo/harbour
