CEDET

Arne Schmitz writes:
> I am trying to figure out how ede works, so that I can use the
> semantic-clang.el better. It seems that it uses the ede facility to
> look for source files. My projects are rather large, but follow a
> regular structure:
>
> Source files reside under $PROJECT_ROOT/modules/*/src/*.cc.
>
> Header files reside under $PROJECT_ROOT/modules/*/include/*/*.h.
>
> Can I teach ede to look under these paths automatically for source and header files?

Use a ede-cpp-root project. For the docs see

(info "(ede) ede-cpp-root")

-David

In particular, if you want support for wildcards, I fear you'll have to do
it yourself i.e. iterate over all entries in the directory using emacs lisp
:-)

(ede-cpp-root-project "mobile3d"
                      :targets '()
                      :file (expand-file-name "~/gitspace/myprojectroot/.
emacs.ws")
                      :directory (expand-file-name
"~/gitspace/myprojectroot/")
                      :locate-fcn 'finder-fn)

(defun finder-fn (name dir)

;; iterate over directories D1..Dn in dir/modules/

;; find name inside Dx/src or Dx/include where x in 1..n

;; again, do the same for include/*

;; finally return full path to found file

  )


Within the finder-fn you may use (ede-expand-filename name dir) to get the
default behavior.


Kind regards,

Thomas :-)
Am 27.04.2012 10:54 schrieb "Arne Schmitz" <arne.schmitz@...>:

> I am trying to figure out how ede works, so that I can use the
> semantic-clang.el better. It seems that it uses the ede facility to look
> for source files. My projects are rather large, but follow a regular
> structure:
>
> Source files reside under $PROJECT_ROOT/modules/*/src/*.cc.
>
> Header files reside under $PROJECT_ROOT/modules/*/include/*/*.h.
>
> Can I teach ede to look under these paths automatically for source and
> header files?
>
> Best regards,
>
> Arne
> --
> Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir
> belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> cedet-semantic mailing list
> cedet-semantic@...
> https://lists.sourceforge.net/lists/listinfo/cedet-semantic
>

I have this in my .emacs, which does something similar to what you want.

(ede-cpp-root-project "insight"
  :file "~/some/path/src/CMakeLists.txt"
  :include-path
  (append '("/graphBuildingCore")
  (let ((default-directory "~/some/path/src/"))
 (delq nil
  (mapcar (lambda (file-or-dir)
(when (file-directory-p file-or-dir)
  ;; Remove the leading dot
  (substring file-or-dir 1)
  ))
  (file-expand-wildcards "./graphBuildingCore/*")))))
  )


Troy

On Fri, Apr 27, 2012 at 5:16 AM, Thomas Karolski <
thomas.karolski@...> wrote:

> In particular, if you want support for wildcards, I fear you'll have to do
> it yourself i.e. iterate over all entries in the directory using emacs lisp
> :-)
>
> (ede-cpp-root-project "mobile3d"
>                       :targets '()
>                       :file (expand-file-name "~/gitspace/myprojectroot/.
> emacs.ws")
>                       :directory (expand-file-name
> "~/gitspace/myprojectroot/")
>                       :locate-fcn 'finder-fn)
>
> (defun finder-fn (name dir)
>
> ;; iterate over directories D1..Dn in dir/modules/
>
> ;; find name inside Dx/src or Dx/include where x in 1..n
>
> ;; again, do the same for include/*
>
> ;; finally return full path to found file
>
>   )
>
>
> Within the finder-fn you may use (ede-expand-filename name dir) to get the
> default behavior.
>
>
> Kind regards,
>
> Thomas :-)
> Am 27.04.2012 10:54 schrieb "Arne Schmitz" <arne.schmitz@...>:
>
> I am trying to figure out how ede works, so that I can use the
>> semantic-clang.el better. It seems that it uses the ede facility to look
>> for source files. My projects are rather large, but follow a regular
>> structure:
>>
>> Source files reside under $PROJECT_ROOT/modules/*/src/*.cc.
>>
>> Header files reside under $PROJECT_ROOT/modules/*/include/*/*.h.
>>
>> Can I teach ede to look under these paths automatically for source and
>> header files?
>>
>> Best regards,
>>
>> Arne
>> --
>> Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir
>> belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de
>>
>>
>> ------------------------------------------------------------------------------
>> Live Security Virtual Conference
>> Exclusive live event will cover all the ways today's security and
>> threat landscape has changed and how IT managers can respond. Discussions
>> will include endpoint security, mobile security and the latest in malware
>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>> _______________________________________________
>> cedet-semantic mailing list
>> cedet-semantic@...
>> https://lists.sourceforge.net/lists/listinfo/cedet-semantic
>>
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> cedet-semantic mailing list
> cedet-semantic@...
> https://lists.sourceforge.net/lists/listinfo/cedet-semantic
>
>