Mel wrote:
On Wednesday 24 December 2008 03:35:07 Matthew Seaman wrote:
B. Cook wrote:
Is there a way to pass make args (other than -m) for each port?
...
If you want options that only apply to specific ports, then you can use
a construct like this:
.if ${.CURDIR:M*/databases/mysql*}
Matthew Seaman wrote:
Mel wrote:
On Wednesday 24 December 2008 03:35:07 Matthew Seaman wrote:
B. Cook wrote:
Is there a way to pass make args (other than -m) for each port?
...
If you want options that only apply to specific ports, then you can use
a construct like this:
.if
Matthew Seaman wrote:
Mel wrote:
On Wednesday 24 December 2008 03:35:07 Matthew Seaman wrote:
B. Cook wrote:
Is there a way to pass make args (other than -m) for each port?
If you want options that only apply to specific ports, then you can use
a construct like this:
.if
On Wednesday 24 December 2008 03:35:07 Matthew Seaman wrote:
B. Cook wrote:
Is there a way to pass make args (other than -m) for each port?
...
If you want options that only apply to specific ports, then you can use
a construct like this:
.if ${.CURDIR:M*/databases/mysql*}
Is there a way to pass make args (other than -m) for each port?
For example if I use -m BUILD_STATIC=YES and -m BUILD_OPTIMIZED=YES for
mysql50-server.. other than remembering that I did that.. is there
someway to have portmaster read its portmaster.rc and get that information?
B. Cook wrote:
Is there a way to pass make args (other than -m) for each port?
For example if I use -m BUILD_STATIC=YES and -m BUILD_OPTIMIZED=YES for
mysql50-server.. other than remembering that I did that.. is there
someway to have portmaster read its portmaster.rc and get that information?
