Hi,
> Viktor,
>
> sorry, but which should I use? I mean, .hbp is for options, so I'd say that
> -mt or -gui have to go there.
.hbp and .hbm uses exactly the same format.
To keep it simple, forget .hbm for now and use one
.hbp file per project (target).
> .hbm is for source files, but how do I state dependencies or the like?
Dependencies are found automatically if you enable -inc mode.
No need to explicitly list dependencies.
[ You can list dependencies using .d files, but lets keep
it simple for now. ]
> Given a bunch of .prg, .ch, .c and .h files, is there some syntax to follow to
> write them inside a .hbm file?
Just list them, whitespace separated.
Except for headers which should not be included.
> And a .hbc file what should it contain? Where do I state needed .a/.lib files,
> or paths and so on?
.hbp = project file. Content is just like command line, but here you can use
multiple lines without command line limitation and undisturbed from
shell features.
.hbm = exact same format as .hbp, you can use it to store common project
properties.
It's simply parsed as 'script file' by hbmk2, it's equivalent to
'@anyfile.ext',
where '@' means simple script file with additional options.
.hbc = config file for libraries. The format is different from .hbp/.hbm and
it's
described in --help and in many examples.
It's optional, and if you have one, it makes it simpler to add libraries
to executable projects, since it's enough to point to .hbc files to
config
header dir, lib dependencies, list of lib file, special lib specific
options, etc.
Given my explanation skills, I'd rather recommend peaking into
any such files inside our contrib area for live examples. You'll
probably understand it much faster.
Check f.e.:
examples\superlib\superlib.hbp
examples\superlib\superlib.hbc
or
examples\rddado\rddado.hbp
examples\rddado\rddado.hbc
Typically you need one .hbp file per project plus optionally
and additional .hbc file.
Brgds,
Viktor
_______________________________________________
Harbour mailing list (attachment size limit: 40KB)
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
