[Edbrowse-dev] One program Two processes

[Karl Dahlke <eklhad@comcast.net>]

this is an incremental step.
Moving towardes a merged solution with one instance of curl,
one set of cookies etc,
there is now just one executable, edbrowse,
which runs as either edbrowse or edbrowse-js depending on its name.
Like gawk and awk in /bin
So still two processes, same interface, same pipes
and messages, same communication, but one target
that is linked to both names.
Eventually edbrowse will spin off js as a thread,
not a fork exec of the same program under a different name,
and then we won't have to worry about replicating or losing cookies etc.
Will also smooth out the differences between linux and windows,
which are considerable any time you say the words fork exec.

Chris I have not touched CMakeLists, could you modify it
to behave the way the makefile does, i.e. no edbrowse.lib
and cp edbrowse edbrowse-js
We have to copy in windows I suppose, no symbolic link,
but this is all temporary anyways, as we eventually won't need edbrowse-js,
so no matter.

Karl Dahlke