just thinking it's about time for breakfast
hmmm.. I just updated my repo
and it seems it fails with some error while building axis
/usr/bin/ld: cannot find -lemc
collect2: ld returned 1 exit status
make: *** [../lib/python/emc.so] Error 1
maybe I borked up the repo, while deleting some dirs, and afterwards updating ?
can't see any other obvious errors
I had this file, from emc2-dev
when I remove it, axis won't link
I don't think I have emc2-dev installed :)
does it work after that fix?
it proceeds further.. thanks
I still get some weird CVS messages while updating though (CVS move away foo.py, it's in the way)
huh.. make builds the docs now too?
yes, it does
rm -r share lib/python
I did before updating
you may need to do that ^^^ as suggested in my mailing-list post last wednesday
the rm -r I mean
what is the directory and filename of the file 'in the way'?
I'll pastebin it.. a bit long
[13:27:50] <alex_joni> http://pastebin.ca/127776
but you did 'rm -r lib/python'
try removing all of lib/ and use -f if necessary
I just did it again
I see the first cvs up -dP that pulls them back in, and the next one to cause the errors again
this is what always seems to happen to jmk
* alex_joni removes all of lib/
it's something about the D// in the above Entries file
I removed the whole lib dir now
ok, that cured it
jepler: 'rm -r lib' made it work OK for me, not lib/python
* jepler goes to have breakfast
sounds like a wise decision ;)
I missed breakfast today .. started with lunch
AXIS & emc2 seem to be working great.. no issues
glad to hear it
max running on two CPUs yet?
nope, no combination of those CPUs and power modules worked.
guess I wasted dollars and dollars
alex_joni: you around?
watching a movie, but I look in here once in a while
the documentation files that you moved into the main cvs module - you didn't delete them from the documents module yet did you?
but I can today
(after the movie ;-)
I want to see what is left after that is done
once _everything_ we need is moved, it will be time to backport the docs stuff to the 2.0 branch
then do some edits on that branch to it describes version 2.0.x
█ █ |
█ █ \
█ █ -
█ █ /
people completely lost it ;)
jmkasunich: did you remove the hal docs?
from documents/ I mean..
ok.. I'll get at removing the other stuff now
(I think - did you cvs up in that module?)
I still want to leave emc1 docs in place..
yeah, I did.. and now after looking closer, it seems to be gone
I'm only thinking of the lyx/emc2 directory
right.. that can go away for good (the whole dir)
hmmm.. how about EMC2_Code_Notes ?
we seem to have not touched that
* alex_joni adds it to emc2/docs/src as included into Master_Developer.lyx
the homing diagram embedded in there (actually the homing chapter) should be pulled out into a separate doc and included in the users or integrators manual
hmm.. we don't seem to have a topic that covers source code
it is in the users manual .. iirc
I think I moved it a while ago
yup: Chapter 7.4 Homing
what name should I add for source ?
or emc2-internals ?
or source ?
* jmkasunich is trying to figure out how to set up a printer
* alex_joni chooses 'code'
it hurts my brain
jmkasunich: ok, won't bother you suring that task.. I know it's a PITA
the printer is a network device, I can access it with a browser and generate a test page
but no clue how to actually print to it - googling now
found a howto....
smb as in samba?
I suspect that it exports a samba printer service..
but it might not be true
it seems to export 6 services
Service NamePort Name
I recognize PCL and Postscript from there
but those are types of the driver
Postscript should be the one you want
any linux program can output postscript (even if through gs)
the trick is figuring out how to tell linux "theres a printer at 192.168.1.20"
I opened the printers dialog, did "new printer", "network printer", "CUPS Printer (ipp)"
and it wants a URI
the uri needs to be ipp://192.168.1.20
I originally tried http://,
and then later ipp: but without the //
still has issues... tried to print a landscape drawing (pdf) and only got 2/3 of it
probably need to rotate it
no, orientation is correct, just shifted off the page
jmkasunich: say when you have 5 minutes..
now is as good as anytime
there were some hal_* documents still left in documents/lyx/emc2
I thought you moved those, but forgot to remove them
now I see they aren't in emc2/docs/ yet
they might start with hal_, but they aren't part of the hal handbook
they are emc specific
hal_halui.lyx , hal_motion.lyx ,
(halui and the motion controller)
right.. both are emc2 specific
hal handbook is not - and will remain that way
halui might fit in the GUI part of the manual, even if it's not fully a GUI but an UI
those should probably be chapters in the EMC2 users manual? or integrators manual maybe
integrators sounds more like it
but there's no such thing yet :/
is emc2/docs/src/hal only hal specific?
no emc2-related hal in there?
I believe so
hmm.. maybe a hal-emc2 folder then?
for emc & hal specific info ?
I haven't looked at halui and hal_motion.lyx
they only have a list of pins
and description what each does
but eventually we'll want to document these interfaces
they are actually chapters about halui and the emc2 motion controller
there is nothing "hal" about them
listing the pins that something exports is just part of documenting that "something"
I'd stick the docs whereever the "something" goes, not in some hal folder
halui goes under gui
ok, so the motion.lyx should go to code/
and halui under gui/
yes for halui
not so sure about motion
code/ is for stuff only developers care about - the actual internals
by reading the file, it describes the HAL pins for io and motion controller
the motion controller is _not_ like that - it is an important part of EMC, and can be described in black-box terms
I agree.. but this is not what this file does
yeah it does
it should be io&motion_pins.lyx
it's not really documenting anything ..
nothing you wouldn't get out of halcmd show pin anyways
* alex_joni is tempted not to add it for now
is it literally just a list of pins?
no details about them or anything?
without descriptions even
then don't add it
it doesn't provide any additional info beyond halcmd show pin, and it will get out of date
it just says which are pins and which params
but that's all of it
and it already is outdated (cause of the spindle moving to motion)
if it had extra details, then the extra info makes the risk of it getting out of date worth taking
dump it then
gotta go, see you tomorrow