Hi Bart,

Ah, OK.  You need to INSTALL Click before you can build Clicky.

If you want to install Clicky in a different directory than Click, that 
too is possible -- --prefix sets the CLicky install dir, 
--with-click=DIR sets the Click install dir (which defaults to PREFIX).

I've implemented the click-pretty functionality you requested. 
Additionally, you can now set what text goes in the element names.  For 
example, if you say

click-pretty --dot -T "<~name>"

you only get element names.

Thanks,
Eddie


Bart Braem wrote:
> Hi Eddie,
> 
> I checked out a fresh git, configured Click there and ran make.
> Then I went to apps/clicky, and ran autoreconf -i
> Then I ran ./configure --prefix=/pathtoclickinstall
> The resulting error:
> 
> '/pathtoclickinstall/share/click/config.mk' not found.
> Are you sure '/pathtoclickinstall' is a Click install directory?
> 
> And of course share/click/config.mk does not exist in that map...
> 
> 
> For click-pretty, I would like to have the element names like this:
> r::RatedSource -> gone::Discard;
> would produce the "r" and the "gone" names in the dot file. That way it is 
> easier to track elements in large configurations, like the ones we produce 
> with firesim. Would that be possible somehow?
> 
> cheers,
> Bart
> 
> On 02 Dec 2009, at 20:13, Eddie Kohler wrote:
> 
>> Hi Bart,
>>
>> I build Clicky with non-root permissions all the time.  Can you send your 
>> Click and Clicky ./configure invocations, and the exact error?
>>
>> On click-pretty, what do you mean by "internal element names"?  The "@" 
>> names that come along with anonymous elements, or names of elements inside 
>> compounds, or...?
>>
>> Cheers,
>> Eddie
>>
>>
>> Bart Braem wrote:
>>> Hi,
>>> Is it possible to build Clicky with non-root permissions? I have tried to 
>>> use the prefix option to configure, but it still refuses to recognise my 
>>> Click installation.
>>> On a related note: I tried click-pretty and noticed it does not use 
>>> internal element names as labels. Am I missing a flag to enable this or 
>>> should I try patching this in?
>>> Best regards,
>>> Bart
>>> _______________________________________________
>>> click mailing list
>>> [email protected]
>>> https://amsterdam.lcs.mit.edu/mailman/listinfo/click
> 
_______________________________________________
click mailing list
[email protected]
https://amsterdam.lcs.mit.edu/mailman/listinfo/click

Reply via email to