All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Williams <steve@icarus.com>
To: linux-hotplug@vger.kernel.org
Subject: fxload source organization
Date: Sat, 09 Jun 2001 02:30:41 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-99205388220304@msgid-missing> (raw)


OK, the first hurdle. How to organize the source and Makefiles for
compiled programs.

My inclination here is to create under admin/ the src/ directory
and put fxload under that. I can make a Makefile in the src/ directory
that builds all the directories, and a Makefile in fxload that builds
the fxload program. This should work out well enough as all compiled
programs can be put under src/.

I predict that the next puzzle will be how to organize the install
process. So far, it looks like a bunch of copies and hand-made
directories, unless you are using the .spec file. Should I stick with
that and update the .spec file appropriately?

-- 
Steve Williams                "The woods are lovely, dark and deep.
steve@icarus.com              But I have promises to keep,
steve@picturel.com            and lines to code before I sleep,
http://www.picturel.com       And lines to code before I sleep."



_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

             reply	other threads:[~2001-06-09  2:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-09  2:30 Stephen Williams [this message]
2001-06-09  2:48 ` fxload source organization David Brownell
2001-06-09  4:42 ` Stephen Williams
2001-06-09 16:35 ` Stephen Williams

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=marc-linux-hotplug-99205388220304@msgid-missing \
    --to=steve@icarus.com \
    --cc=linux-hotplug@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.