On Thu, Dec 8, 2011 at 4:15 PM, Charlie Poole <[email protected]> wrote:
> On Thu, Dec 8, 2011 at 12:48 PM, Fulko Hew <[email protected]> wrote: > ... snip ... > > Lets say my library ('mylib') consists of only two things right now: > > myTypeA and myTypeB (that belong to my company 'xyz'. > > And to use/test these library components I have a main app called > 'tester'. > > > > So what I was expecting to do was to create the following directory > > structure: > > > > ./com.xyz.mylib/ > > myTypeA.cs > > myTypeb.cs > > ./com.xyz.tester/tester.cs > > > > a) is this a valid structure? > > Sure, although the backwards naming of components something that is > part of the Java culture and a little foreign to most C# folks. That's OK. > Then what _is_ the recommended directory structure? > > b) what compiler directives do I use to build my libraries? > ... snip ... > gmcs -t:library -out:mylib.dll myTypeA.cs myTypeB.cs > gmcs -t:exe -out:tester -r:mylib.dll tester.cs > Thanks, your help has gotten me past my original hurdle, but, is this kind of stuff documented anywhere? or is it just something you have to figure out and/or ask about like I did? In a related question... how would I go about compiling the components separately and then 'link' them together into a library? (ie. the traditional 'don't recompile unless the source file changed' approach.) This would all be much easier if you were using MonoDevelop rather > than working at the command line, but I suppose you're like me and > want to do it the hard way first. :-) > Your right. I'm an engineer and not a 'mouse jockey', and I need to know whats going on. Especially because I can't expect the 'next guy' to be using exactly the same tools (or platform) as I am. Heck... I didn't even know that MonoDevelop existed! None of the introductory docs _I_ read mentioned it. Fulko
_______________________________________________ Mono-list maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-list
