Skip to content
Snippets Groups Projects
Select Git revision
  • 9d1b3eed26e2fcc7780a5b01c26d695d1800443f
  • master default
  • rsa-crt-hardening
  • chacha96
  • fat-library
  • versioned-symbols
  • curve25519
  • dsa-reorg
  • aead-api
  • set_key-changes
  • poly1305
  • aes-reorg
  • nettle-2.7-fixes
  • size_t-changes
  • ecc-support
  • experimental-20050201
  • lsh-1.4.2
  • nettle_3.1.1_release_20150424
  • nettle_3.1_release_20150407
  • nettle_3.1rc3
  • nettle_3.1rc2
  • nettle_3.1rc1
  • nettle_3.0_release_20140607
  • nettle_2.7.1_release_20130528
  • nettle_2.7_release_20130424
  • nettle_2.6_release_20130116
  • nettle_2.5_release_20120707
  • converted-master-branch-to-git
  • nettle_2.4_release_20110903
  • nettle_2.3_release_20110902
  • nettle_2.2_release_20110711
  • nettle_2.1_release_20100725
  • camellia_32bit_20100720
  • nettle_2.0_release_20090608
  • nettle_1.15_release_20061128
  • after_experimental_merge_20060516
  • head_before_experimental_merge_20060516
37 results

buffer.c

Blame
  • Forked from Nettle / nettle
    Source project has a limited visibility.
    .how_to_create_modules 1.14 KiB
    How to create Pike modules
    ==========================
    
    o You need a name for your module, for our purposes, let us assume you 
       want to create the module "modulen".
    
    o Create the dir src/modules/modulen
    
    o Copy the Makefile.in from src/modules/Gz and modify it.
      Set the macro OBJS to all objectfiles in your module.
      Set the macro MODULE_LDFLAGS to all needed -L<libdir> -R<libdir>
      options followed by all needed -l<lib> options.
      If you want your module to always be linked statically, modify
      @dynamic_module_makefile@ to @static_module_makefile@.
      The Makefile.in need not contain any dependencies.
    
    o You need a testsuite.in, even if it is just an empty one.
    
    o You need a configure.in
      Your configure.in should test for ALL features you need.
      Your configure.in should contain the line
    	sinclude(../module_configure.in)
      Do not trust the global configure tests to do things for you.
    
    o All C/C++ files should include "global.h" as the first included file.
    
    o When building the your module the first time you need to:
      1) run autoconf
      2) do 'make depend' from your build dir
      3) re-run configure from your build dir
      4) make (in your build dir)