[Caml-list] il est enfin la
Windows 7 est arrive c'est la meilleure version de windows a ce jour. Vous avez le choix de l'acheter sur les sites officiels et payer 300 euros pour la version ultime. Ou l'obtenir en toute legalite en francais avec mise a jour incluse pour moins de 100 euros. Il y a meme un coupon de reduction sur le site pour payer encore moins cher que prevu. N'hesitez pas, cliquez sur http://rivognedoss.net/ Bon week end. Thierry ___ Caml-list mailing list. Subscription management: http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list Archives: http://caml.inria.fr Beginner's list: http://groups.yahoo.com/group/ocaml_beginners Bug reports: http://caml.inria.fr/bin/caml-bugs
[Caml-list] Simple ocamlbuild example for C stubs?
Hello. I'm trying to build a .cma with C stubs with ocamlbuild. Linking and includes are supposed to be set to non-standard directories. Is there a state-of-the-art, and *simple* example lying around? Is there an ocamlbuild plugin that is more generic than the one on the Wiki http://brion.inria.fr/gallium/index.php/Ocamlbuild_example_with_C_stubs which I unfortunately find quite obscure. All the best, -- Guillaume Yziquel http://yziquel.homelinux.org/ ___ Caml-list mailing list. Subscription management: http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list Archives: http://caml.inria.fr Beginner's list: http://groups.yahoo.com/group/ocaml_beginners Bug reports: http://caml.inria.fr/bin/caml-bugs
[Caml-list] Re: Simple ocamlbuild example for C stubs?
On 28-11-2009, Guillaume Yziquel guillaume.yziq...@citycable.ch wrote: Hello. I'm trying to build a .cma with C stubs with ocamlbuild. Linking and includes are supposed to be set to non-standard directories. You probably need to add some 'A-ccopt; Ayour-option' to the good tag. Can you give more details/actual layout of your myocamlbuild.ml ? Regards, Sylvain Le Gall ___ Caml-list mailing list. Subscription management: http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list Archives: http://caml.inria.fr Beginner's list: http://groups.yahoo.com/group/ocaml_beginners Bug reports: http://caml.inria.fr/bin/caml-bugs
[Caml-list] solicitation for ocamlbuild examples to go in a new repository
Hello Ocaml-folk-- As the previous and many other posts on this list demonstrate, there is a need for a collection of ocamlbuild examples which can be adapted to various setting. I've started such a project (at Sylvain LeGall's suggestion) at http://forge.ocamlcore.org/projects/obuild-examples/ I hope that the community will take a bit of time to sumbit examples. I'd be very happy if others were interested in joining the project, but it might be easiest just to email examples directly to me. An ideal package from my perspective would have - a short description of what it does, just a sentence or two. - a commented myocamlbuild.ml file - the corresponding _tags file I hope to get examples of all levels, from very basic to advanced. However, I think that there is a distinct need for simple examples which do one or two interesting things (a flood of 10 page myocamlbuild files isn't going to help people get off the ground). Thanks, Erick ___ Caml-list mailing list. Subscription management: http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list Archives: http://caml.inria.fr Beginner's list: http://groups.yahoo.com/group/ocaml_beginners Bug reports: http://caml.inria.fr/bin/caml-bugs
Re: [Caml-list] Partially hiding modules in packages
blue storm a écrit : Regarding your original problem, I've had the same needs and came up with a slightly different solution : in order to avoid the additional indirection level related to -pack (Foobar.Foo), is used a flattened representation by adding a foobar.ml file containing only : include Foo (and possibly include of other modules in the package). Then the foobarl.mli is : type foo_t val initial : foo_t val show : foo_t - string And values can be referred with Foobar.foo, instead of Foobar.Foo.foo. Of course this is only useful if you don't want the user to see the internal module hierarchy, wich may not be what you had in mind. Where do you put the foobar.ml? I've been trying it all over, I do not see how you can flatten something that you pack. Do you put foobar.ml at the same level of your directory foobar/, or in you directory foobar/ ? Or am I understanding you wrong? All the best, -- Guillaume Yziquel http://yziquel.homelinux.org/ ___ Caml-list mailing list. Subscription management: http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list Archives: http://caml.inria.fr Beginner's list: http://groups.yahoo.com/group/ocaml_beginners Bug reports: http://caml.inria.fr/bin/caml-bugs
Re: [Caml-list] Re: Simple ocamlbuild example for C stubs?
Sylvain Le Gall a écrit : On 28-11-2009, Guillaume Yziquel guillaume.yziq...@citycable.ch wrote: Hello. I'm trying to build a .cma with C stubs with ocamlbuild. Linking and includes are supposed to be set to non-standard directories. You probably need to add some 'A-ccopt; Ayour-option' to the good tag. Can you give more details/actual layout of your myocamlbuild.ml ? OK. Yes, I could meddle with my myocamlbuild.ml file. My myocamlbuild.ml file is the same as the one on the wiki: http://brion.inria.fr/gallium/index.php/Using_ocamlfind_with_ocamlbuild But I mean, if I'm supposed to write a myocamlbuild.ml for every project I make, I might as well use Makefiles, as below. I was wondering if there was a myocamlbuild.ml that would solve the C stub problem and bottleneck. For instance, being able to _tag in the tags file for a given .c file the directories in which to look for headers (here /usr/share/R/include), and for .o files, all linking information (here, /usr/lib/R/lib/libR.so). The ideal would be to have all that available only from _tags. Because if you need to write a myocamlbuild.ml for each and every project, you might as well write Makefiles... That's the point of a generic plugin. yziq...@seldon:~/git/ocaml-r$ cat Makefile RLIBDIR=/usr/lib/R/lib RINCLUDES=-I . -I /usr/share/R/include INCLUDES= -I +ocamldoc -I `ocamlc -where`/caml $(RINCLUDES) COMPFLAGS=$(INCLUDES) LINKFLAGS=$(INCLUDES) -ccopt -L$(RLIBDIR) -cclib -lR LINKFLAGS_BYTE=$(INCLUDES) -ccopt -L$(RLIBDIR) -cclib -lR all: build #build: r.cma r.cmxa oCamlR.cma oCamlR.cmxa build: r.cma r.cmxa r.cma: dllr_stubs.so camlobjs ocamlc -a -dllpath /usr/lib/R/lib -dllib dllr_stubs.so -dllib libR.so -o r.cma r.cmo r.cmxa: dllr_stubs.so camlobjs ocamlopt -a -ccopt -L/usr/lib/R/lib -cclib -lr_stubs -cclib -lR -o r.cmxa r.cmx oCamlR.cma: camlobjs ocamlc -a -o oCamlR.cma oCamlR.cmo oCamlR.cmxa: camlobjs ocamlopt -a -o oCamlR.cmxa oCamlR.cmx camlobjs: standard.ml # ocamlbuild -classic-display r.cmo r.cmx oCamlR.cmo oCamlR.cmx ocamlbuild -classic-display r.cmo r.cmx cp _build/r.cmi . cp _build/r.cmo . cp _build/r.cmx . cp _build/r.o . # cp _build/oCamlR.cmi . # cp _build/oCamlR.cmo . # cp _build/oCamlR.cmx . standard.ml: r/standard.R R --silent --vanilla --slave r/standard.R r/standard.ml r_stubs.o: r_stubs.c ocamlopt -ccopt -Wall $(COMPFLAGS) -ccopt -fPIC -c $ libr_stubs.a: r_stubs.o ar rcs libr_stubs.a r_stubs.o dllr_stubs.so: libr_stubs.a r_stubs.o ocamlmklib -o r_stubs r_stubs.o clean: rm -f r/tandard.ml rm -f *.o *.so *.a *.cmi *.cmo *.cmx *.cma *.cmxa ocamlbuild -clean test: build ocaml -init ocamlinit install: cp META *.a *.cm[ai] *.cmxa /usr/lib/ocaml/R/ cp dllr_stubs.so /usr/lib/ocaml/stublibs/ All the best, -- Guillaume Yziquel http://yziquel.homelinux.org/ ___ Caml-list mailing list. Subscription management: http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list Archives: http://caml.inria.fr Beginner's list: http://groups.yahoo.com/group/ocaml_beginners Bug reports: http://caml.inria.fr/bin/caml-bugs
Re: [Caml-list] solicitation for ocamlbuild examples to go in a new repository
Erick Matsen a écrit : Hello Ocaml-folk-- As the previous and many other posts on this list demonstrate, there is a need for a collection of ocamlbuild examples which can be adapted to various setting. I've started such a project (at Sylvain LeGall's suggestion) at http://forge.ocamlcore.org/projects/obuild-examples/ I hope that the community will take a bit of time to sumbit examples. The point is, in my humble opinion, that we do need examples, but we'd better try to have a generic plugin that solves most of the use cases. And *precise* documentation of ocamlbuild to be able to write such a plugin, or other plugins. For now, the pain/benefit ratio of writing ocamlbuild plugins is clearly not worth it. Due to lack of documentation. I'd be very happy if others were interested in joining the project, but it might be easiest just to email examples directly to me. An ideal package from my perspective would have - a short description of what it does, just a sentence or two. - a commented myocamlbuild.ml file - the corresponding _tags file If you receive such examples, it would be useful to make them as generic as possible. There's no point, from a tutorial point of view, in having 'complex' myocamlbuild plugins that you have to wrap your head around in order to reuse. I'm thinking about examples on the wiki pages. I hope to get examples of all levels, from very basic to advanced. However, I think that there is a distinct need for simple examples which do one or two interesting things (a flood of 10 page myocamlbuild files isn't going to help people get off the ground). Yes. Exactly. Thanks, Erick There's definitely a know how out there. I'm thinking of bluestorm who helped me out with the .inferred.mli target for the plugin on the wiki. http://brion.inria.fr/gallium/index.php/Using_ocamlfind_with_ocamlbuild I gave feedback, and its been since then on the wiki page above. Maybe I'm mistaken, but this plugin hasn't evolved much since then. I'm fairly disappointed that it has not been augmented to fit the needs of C stubs in a generic way. All the best, -- Guillaume Yziquel http://yziquel.homelinux.org/ ___ Caml-list mailing list. Subscription management: http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list Archives: http://caml.inria.fr Beginner's list: http://groups.yahoo.com/group/ocaml_beginners Bug reports: http://caml.inria.fr/bin/caml-bugs
[Caml-list] Memocode 2010 First Call for Papers
MEMOCODE 2010 First Call for Papers The eighth ACM-IEEE International Conference on Formal Methods and Models for Codesign (MEMOCODE 2010) will be held on July 26-28, 2010 in Grenoble, France. http://www.memocode-conference.com IMPORTANT DATES: Abstract submission deadline: February 26, 2010 Paper submission deadline: March 5, 2010 Notification of acceptance:April 30, 2010 Poster submission deadline:May 14, 2010 Notification for Posters: May 28, 2010 Final Version for Papers: May 28, 2010 The eighth MEMOCODE conference will attract researchers and practitioners who create methods, tools, and architectures for the design of hardware/software systems. These systems face increasing design complexity including tighter constraints on timing, power, costs, and reliability. MEMOCODE seeks submissions that present novel formal methods and design techniques addressing these issues to create, refine, and verify hardware/software systems. We also invite application-oriented papers, and especially encourage submissions that highlight the design perspective of formal methods and models, including success stories and demonstrations of hardware/software codesign. Furthermore, we invite poster presentations describing ongoing work with promising preliminary results. Topics of interest for regular submissions include but are not limited to - system- and transaction-level modeling and verification, abstraction and refinement between different modeling levels, formal, semi-formal, and specification-driven verification, - design and verification methods for composition of concurrent systems: multi-core platform architectures, systems-on-chip, networks-on-chip, - non-traditional and domain-specific design languages for hardware and software, novel models of computation, and new design paradigms that unify hardware and software design, - system-level estimation of performance and power in heterogeneous hardware/software architectures, - applications and demonstrators of formal design methodologies and case studies of innovative system-level design flows, and - modeling and reuse of intellectual property at system-level. PROCEEDINGS: Conference proceedings will be published by the IEEE Computer Society. SUBMISSION: Submissions of research and experience papers will only be accepted through the conference web site. Papers must not exceed 10 pages and must be formatted following IEEE Computer Society guidelines. Submissions must be written in English, describe original work, and not substantially overlap papers that have been published or are being submitted to a journal or another conference with published proceedings. Poster submissions should consist of an abstract of at most 250 words. The abstract will be distributed to the conference attendants but will not be published. Note that the poster deadline is different from the paper deadline. DESIGN CONTEST: MEMOCODE will again have a design contest. The contest will start March 1, 2010. The deadline for submission is 31 March 2010 and the notification of the results is on May 14, 2010. The conference will sponsor at least two prize categories, each with a significant cash award. We awarded a $1000 prize in each of the two categories in 2009. Each team that submits a complete and working entry will be invited to submit for review a 2-page abstract for the formal conference proceedings; winning teams will be invited to contribute a 4-page short paper. Each team submitting a completed and working entry will also receive a commemorative plaque with their name and results. Please refer to the conference website for more information and updates. TUTORIALS: MEMOCODE will feature tutorials related to hardware/software codesign. Please send your tutorial proposals to alain.gira...@inria.fr. General Chair: Klaus Schneider (Kaiserslauten) Finance Chair: James Hoe (CMU) Program Chairs: Barbara Jobstmann (CNRS) and Luca Carloni (Columbia) Design Contest: Joel Emer (Intel) and Forrest Brewer (UCSB) Local Chairs: Saddek Bensalem (UJF/CEA) and Christian Fabre (CEA) Tutorial Chair: Alain Girault (INRIA) Program Committee David Atienza (EPFL) Twan Basten (Eindhoven) Tevfik Bultan (UCSB) Robert de Simone (INRIA) Rainer Doemer (UCI) Rolf Drechsler (Bremen) Stephen Edwards (Columbia) Franco Fummi (Verona) Thierry Gautier (INRIA) Ganesh Gopalakrishnan (Utah) Josef Haid (Infineon) Franjo Ivancic (NEC) Christoph Kirsch (Salzburg) Daniel Kroening (Oxford) Yassine Lakhnech (UJF) Luciano Lavagno (Torino) Elizabeth Leonard (NRL) Rishiyur Nikhil (Bluespec, Inc.) John O'Leary (Intel) Roberto Passerone (Trento) Diego Puschini (CEA) Jan Reineke (UC Berkeley) Patrick Schaumont (VirginiaTech) Klaus Schneider (Kaiserslautern) Sanjit Seshia (UC
